# SIGNALS_TIMEOUT

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

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

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

Signals did not answer in time when Ovok forwarded a reading delivered by the FHIR store. The reading may or may not have reached Signals. You see this in the delivery log of the project's automatic send, not in a user request.

## Troubleshooting [#troubleshooting]

1. Wait for the FHIR store to deliver the Observation again. It retries on its own, so you do not need to resend it.
2. Check whether other Signals calls for the project are slow or failing too. If they are, Signals is the cause, and the deliveries recover once it does.
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. Do not resend the Observation yourself unless the deliveries have stopped.

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