SIGNALS_BUSY

Signals busy: what the SIGNALS_BUSY error means and how to fix it.

HTTP 503. Problem type: https://docs.ovok.com/errors/signals-busy.

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

  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

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

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 explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page