Skip to content
Error codes · realuptime errors ingest

RU-4016: Inbound release webhook rate limited

One inbound release 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-4016" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • A deploy platform retrying a webhook delivery aggressively after a transient failure.

How to fix it

  1. Honor Retry-After.
  2. Check the connector's audit log for repeated deliveries of the same deployment.

Related codes

  • RU-4013: Inbound release webhook token not recognized

Still stuck?

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