Discord error 20028: Channel write rate limit

A channel-scoped write limit has been exceeded. Unlike the per-route buckets described in the rate limit docs, this limit is applied to a specific channel and is shared across everyone writing to it. Discord does not publish the exact threshold; it is a server-side protection that tends to trigger when a channel receives a burst of writes (messages, edits, reactions, thread operations) far above normal, or when a channel is under active abuse.

You will see it most often in shared-bucket situations: several bots or webhooks posting to the same log channel, a bot that mirrors a high-traffic source into one channel, or a reaction-role setup that adds many reactions to one message at once. The X-RateLimit-Scope: shared header is a hint that the limit is not specific to your bot.

{
  "message": "The resource is being rate limited.",
  "retry_after": 4.21,
  "global": false,
  "code": 20028
}

Design around per-channel throughput from the start: one outbound queue per channel, batching where the content allows it, and a hard ceiling on writes per minute. Avoid channels that are simultaneously written to by several independent systems.

Per-channel throughput problems compound quietly: the log channel that three services share works for months, then a traffic spike puts all three into backoff at once. Budget writes per channel the way you budget REST calls overall, per the bucket model in http 429 and the pacing guidance in chatbot API rate limiting.