# SIGNALS_BUSY

Canonical page: https://docs.ovok.com/errors/signals-busy

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

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

Signals asked Ovok to wait, so a reading delivered by the FHIR store was not forwarded. `retryAfterSec` and the `Retry-After` header say how long to wait. You see this in the delivery log of the project's automatic send, not in a user request.

## Troubleshooting [#troubleshooting]

1. Wait for `retryAfterSec` seconds. The FHIR store delivers the Observation again by itself, so you do not need to resend it.
2. Check for a burst of new Observations, such as an import or many devices uploading at once. Spread large batches out over time.
3. Fix a longer stall soon. A reading is forwarded only within about an hour of being saved, and an older delivery is dropped.

## Retry safely [#retry-safely]

Retrying is safe. Signals treats a reading it already holds as received, so a repeated delivery does not store it twice. Wait the full `retryAfterSec` before each attempt.

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