# SIGNALS_BACKLOG_FULL

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

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

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

Signals has not been taking device readings for a while, and Ovok already holds as many readings for it as it allows. To keep that backlog bounded, Ovok refused this request before storing anything from it. It affects the device ingest routes only.

## Troubleshooting [#troubleshooting]

1. Wait for `retryAfterSec`, which the `Retry-After` header repeats. It is 30 to 45 seconds.
2. Send the whole request again unchanged. Nothing from it was stored, so no reading is lost or stored twice.
3. If refusals go on for more than the hold window (10 minutes by default), check that Signals is answering.

## Retry safely [#retry-safely]

Retrying is safe: the refused request stored nothing. Wait the full `retryAfterSec`, add a random pause, and never retry in a tight loop.

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