# PROJECT_UNAVAILABLE

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

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

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

Ovok could not look up which project a resident of the shared Signals tenant belongs to, so it did not act on the alert or episode event. The failure is on Ovok's side. The event is fine, and Signals should deliver it again.

## Troubleshooting [#troubleshooting]

1. Let Signals retry the same delivery. Wait the seconds in the `Retry-After` header first.
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 every delivery fails for more than a few minutes, the lookup is down for all events. Ask the operator of the Ovok environment to check it.

## Retry safely [#retry-safely]

Retry after the `Retry-After` wait. Nothing was done for this event, 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.
