DELIVERY_FAILED
Alert event not delivered: what the DELIVERY_FAILED error means and how to fix it.
HTTP 502. Problem type: https://docs.ovok.com/errors/delivery-failed.
What this means
Ovok received an alert event from Signals for omni-channel alerts, but a provider refused or missed at least one send: the email provider answered with an error, or the push provider failed for now. The people it did reach are recorded, so they are not told again. You see this in the delivery log of the project's alerts subscriber, not in a user request.
Troubleshooting
- Wait for Signals to deliver the event again. It retries on its own, and only the sends that failed go out.
- Check the project's email provider and push provider in the Console. A provider that keeps failing is the cause.
Retry safely
Retrying is safe. Each send is recorded under the event's webhook-id, so a repeated delivery never tells anyone twice.
If the problem persists
Share the HTTP status, problem type, request path, response timestamp and traceId with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The Error responses guide explains the response fields, and the machine-code registry lists every endpoint-specific type.
Last updated on