# DELIVERY_FAILED

Canonical page: https://docs.ovok.com/errors/delivery-failed

**HTTP 502.** Problem type: [`https://docs.ovok.com/errors/delivery-failed`](https://docs.ovok.com/errors/delivery-failed).

## What this means [#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 [#troubleshooting]

1. Wait for Signals to deliver the event again. It retries on its own, and only the sends that failed go out.
2. Check the project's email provider and push provider in the Console. A provider that keeps failing is the cause.

## Retry safely [#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 [#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](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
