# SETTING_WIRING_FAILED

Canonical page: https://docs.ovok.com/errors/setting-wiring-failed

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

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

`SIGNALS_SEND_AUTO`, `SIGNALS_ANNOTATE_OBSERVATIONS` and `SIGNALS_MTLS_ENABLED` switch something on outside the project, and Ovok could not switch it. For `SIGNALS_MTLS_ENABLED` that includes a Signals that does not keep the switch. Ovok undid what it had changed, and nothing was saved. The setting keeps its earlier value. It answers 500 when this server has no public callback address set up, and 502 when the project has no Signals tenant of its own, or Signals could not be read or changed.

## Troubleshooting [#troubleshooting]

1. Retry the same request after a short wait. Ovok undoes its changes before it answers, so a repeat normally starts clean.
2. Read the project settings to confirm the setting did not change. A failed switch leaves the saved value as it was.
3. Check whether other Signals calls for the project fail with `SIGNALS_UNAVAILABLE`. If they do, wait for Signals to recover, then retry.
4. Ask the operator of the environment to check its public callback address if the error persists while Signals works. Without it, the environment cannot tell Signals or the FHIR store where to deliver.

## Retry safely [#retry-safely]

Retry the same request. A repeated switch-on sets up any wiring that is missing. If another change to the same switch is running, wait for it to finish before you retry.

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