# HL7_TIMEOUT

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

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

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

No HL7 agent answered within 10 seconds when Ovok sent a reading for this connection. Most often the agent is offline: stopped, or its host lost its outbound HTTPS connection. You see this in the connection's delivery log, not in a user request.

## Troubleshooting [#troubleshooting]

1. Check the connection's agent status with `GET /v1/hl7-connections/<id>`. `disconnected` means the agent is not signed in.
2. Restart the agent on the hospital's host, and check that the host can reach the Ovok API over HTTPS (443).
3. Wait for the next attempt once the agent is back. Ovok retries for about 34 minutes, so a short outage recovers on its own.
4. For a longer outage, resend the readings that were missed once the agent is connected again.

## Retry safely [#retry-safely]

Retrying is safe. Every attempt sends the same message with the same control id (MSH-10), so the receiver can drop a repeat.

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