Skip to content
Error codes · realuptime errors ingest

RU-4014: Inbound release payload not understood

The body of an inbound release webhook could not be read as a supported deploy platform's event, or the event type does not represent a live deployment (Vercel's deployment.succeeded, deployment.promoted, deployment.ready). The `error` field says which.

On the wire

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

Common causes

  • The Vercel webhook was configured for an event other than Deployment Succeeded.
  • Sending a body that is not JSON, or not Vercel's documented envelope (`type`, `payload.deployment`).

How to fix it

  1. Read the `error` field for the specific reason.
  2. In Vercel's webhook settings, select Deployment Succeeded and point it at this connector's URL.

Related codes

  • RU-4013: Inbound release webhook token not recognized
  • RU-4015: Inbound release signature missing or wrong

Still stuck?

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