# SIGNALS UNDO FAILED

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

**HTTP 503.** Stable Problem Details type: [`https://docs.ovok.com/errors/signals-undo-failed`](https://docs.ovok.com/errors/signals-undo-failed).

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

The Signals change could not be recorded or undone and requires operator reconciliation. Clients should branch on `type` and `status`, not on human-readable `detail` text.

## Troubleshooting [#troubleshooting]

Stop repeating the write. Preserve `traceId` and ask an administrator to inspect rollback and audit state. Compare the request with the relevant endpoint's documentation and confirm the authenticated project and environment. Record the request path and `traceId` before escalating; the identifier lets an administrator find server-side context without sharing credentials or patient data.

## Related endpoint guidance [#related-endpoint-guidance]

The routes that answered this error were removed with Ovok's `/v1/signals` API. A new Signals API is being designed; see [Working with Signals](/signals/connected-ovok).

## Retry safely [#retry-safely]

For a 5xx response, wait for `Retry-After` when present and retry with bounded backoff. Before replaying a write, read the affected resource or operation state to avoid duplicate effects. Follow endpoint-specific idempotency and concurrency guidance. Do not retry in a tight loop or use a broader permission or project setting to bypass the check.

## 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 sensitive patient data from the report. The [Error responses guide](/errors) explains the response fields, while the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type audited for this release.