# SECRET_UNAVAILABLE

Canonical page: https://docs.ovok.com/errors/secret-unavailable

**HTTP 503.** Problem type: [`https://docs.ovok.com/errors/secret-unavailable`](https://docs.ovok.com/errors/secret-unavailable).

## What this means [#what-this-means]

Ovok could not read the secret it checks a webhook delivery against, so it could not tell whether the delivery is genuine. The delivery was not processed. The failure is on Ovok's side.

## Troubleshooting [#troubleshooting]

1. Let the sender retry. Wait the seconds in the `Retry-After` header, then resend. The FHIR store and Signals both retry failed deliveries.
2. Keep the endpoint enabled. Signals switches an endpoint off after five days of failed deliveries, and a short outage needs no change.
3. If the failure lasts on the shared Signals route, the Ovok environment may have no shared webhook secret configured. Ask the operator of the environment to set it.
4. If it lasts on a project route, the project's stored secret cannot be read. Ask the operator to check the project's Signals setup.

## Retry safely [#retry-safely]

Retry after the `Retry-After` wait. Nothing was processed, so a retry cannot duplicate anything.

## 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.
