# SIGNALS_ENROLMENT_FAILED

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

**HTTP 502.** Problem type: [`https://docs.ovok.com/errors/signals-enrolment-failed`](https://docs.ovok.com/errors/signals-enrolment-failed).

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

The first reading of a resident enrols the resident in Signals, and that enrolment failed, so the reading was not forwarded. 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, and the next attempt tries the enrolment again.
2. Enrol the resident yourself with the `$enable-signals` operation on the Patient. It is all or nothing and safe to repeat, and an enrolled resident answers with its Signals id.
3. Check whether other Signals calls for the project fail too, such as `SIGNALS_UNAVAILABLE`. If they do, the enrolment recovers once Signals does.

## Retry safely [#retry-safely]

Retrying is safe. A failed enrolment leaves nothing half done. A reading is forwarded only within about an hour of being saved, so enrol the resident soon if the retries keep failing.

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