# SIGNALS AUDIT FAILED

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

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

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

Ovok could not record an audit event, so the requested Signals change was not applied. Clients should branch on `type` and `status`, not on human-readable `detail` text.

## Troubleshooting [#troubleshooting]

Preserve `traceId` and read the setting to confirm it stayed unchanged. Check audit storage health before retrying the write. 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.