Skip to content
Error codes · Status pages & incidents

RU-5007: Inbound incident webhook rate limited

One inbound webhook token received more requests in a minute than its budget allows. The Retry-After header says how long to back off. Each token has its own budget, so one noisy sender cannot starve another.

On the wire

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

Common causes

  • An alerting rule with a very short repeat interval.
  • A grouping configuration that sends one request per alert instead of batching.

How to fix it

  1. Honor Retry-After.
  2. Group alerts in the sender (Alertmanager group_by, Grafana notification policies) so one request carries many alerts; up to 50 per request are accepted.

Related codes

  • RU-5004: Inbound incident webhook token not recognized

Still stuck?

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