# FEATURE_DISABLED

Canonical page: https://docs.ovok.com/errors/feature-disabled

**HTTP 403.** Problem type: [`https://docs.ovok.com/errors/feature-disabled`](https://docs.ovok.com/errors/feature-disabled).

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

The route needs a feature that is switched off for the Signals tenant, so Signals refused the request and changed nothing. `data.feature` names the feature, such as `episodicAlerts` for episodes and alert notes.

## Troubleshooting [#troubleshooting]

1. Read `data.feature`.
2. Ask a manager of the tenant whether the feature should be on. It is switched in the tenant's settings, not per request.
3. Check whether the project shares its tenant with others. A shared tenant has one setting for every project on it.
4. Use a route that does not need the feature, such as the alert list instead of episodes, if it should stay off.

## Retry safely [#retry-safely]

Do not retry until the feature is on. An unchanged request returns the same error, and nothing is written.

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