# FEATURE_NOT_CONFIGURED

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

**HTTP 501.** Stable Problem Details type: [`https://docs.ovok.com/errors/feature-not-configured`](https://docs.ovok.com/errors/feature-not-configured).

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

Ovok recognizes the requested feature or integration, but it is not enabled or cannot be configured in this deployment. For example, a wearable provider may return this error when wearable secret storage is unavailable.

## Troubleshooting [#troubleshooting]

Confirm that the request is going to the intended environment and that the integration is supported there. Ask the project administrator to check the endpoint's setup requirements, whether the integration is enabled, and whether its required configuration is available. Do not put integration credentials in a support message or error report.

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

Use these pages to check the route, project settings, and request requirements associated with this error:

- [Set up wearable providers](/wearables/set-up-providers)
- [Wearables API reference](/wearables/api-reference#provider-setup)

## Retry safely [#retry-safely]

A retry with the same request will not configure the feature. Retry after an administrator confirms that setup has changed, using the endpoint's documented request format.

## 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. Do not include access tokens or sensitive patient data. The [Error responses guide](/errors) explains the response fields and field-level errors.