# SETTING_NOT_AVAILABLE

Canonical page: https://docs.ovok.com/errors/setting-not-available

**HTTP 409.** Problem type: [`https://docs.ovok.com/errors/setting-not-available`](https://docs.ovok.com/errors/setting-not-available).

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

You tried to switch on a setting this project cannot have on yet. Nothing was changed. Switching a setting off is always allowed.

- `SIGNALS_SEND_AUTO` or `SIGNALS_ANNOTATE_OBSERVATIONS`: both need the project to have a Signals tenant of its own, and this project uses the shared one.
- `SIGNALS_MTLS_ENABLED`: it needs a Signals tenant of the project's own, an environment whose edge forwards client certificates, and at least one registered client certificate (`POST /v1/signals/certs`).
- The clinician alert digest (`practitionerAlertDigest` on `PUT /v1/patient-sharing/settings`): it needs Signals annotations, patient sharing and practitioner sharing all on.

## Troubleshooting [#troubleshooting]

For the clinician alert digest, switch on whichever of Signals annotations, patient sharing and practitioner sharing is off, then switch the digest on again. For the Signals switches:

1. Check whether the project has its own Signals tenant. Sub-projects created through Ovok get one when they are created.
2. Ask Ovok to move the project to a tenant of its own if it is an older project. A project that already has residents on the shared tenant stays on it until Ovok moves it.
3. Switch the setting on in a project that has its own tenant, if you do not need to move this one.
4. For `SIGNALS_MTLS_ENABLED`, register a client certificate first, then switch it on again.

## Retry safely [#retry-safely]

Do not retry the switch-on until what it needs is in place: the project's own tenant, or the digest's three settings. An unchanged request returns the same error. The setting keeps its earlier value.

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