Skip to content
Error codes · realuptime errors ingest

RU-4021: Tracker webhook rate limited

One tracker connection's inbound webhook received more deliveries in a minute than its budget allows. The Retry-After header says how long to back off.

On the wire

Ships with HTTP status 429, carrying "code": "RU-4021" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • A provider automation misconfigured to fire on every field change rather than just status/assignee/comment.
  • A retry storm from a earlier outage on realuptime's side, replaying the provider's backlog of undelivered webhooks at once.

How to fix it

  1. Honor Retry-After; the provider's own retry (GitHub and Linear both retry a non-2xx automatically) will succeed once the window clears.
  2. Narrow the Jira Automation rule's trigger conditions if it is firing far more often than the tracked issue actually changes.

Related codes

  • RU-4018: Tracker webhook not recognized

Still stuck?

Ask support and mention RU-4021: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.