Skip to content

WhatsApp media download policy cannot be tuned #103

Description

@SirLouen

Current state: mediaSweepBatch is read straight from a package constant inside sweepOnce so it has no seam at all, and Register never sets the interval or timeout that mediaFetcherConfig does expose. Inbound media is capped near three hundred downloads an hour for the entire install across every tenant, and a media id is retried for seven days.

Proposal: read the batch, interval, timeout and retry window from the environment, defaults as today.

Trigger: a burst of images for one tenant no longer starves every other tenant behind it.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deferredIssues that have been found during a feat dev and were deferred for later

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions