# SIGNALS_TENANT_NOT_OWN

Canonical page: https://docs.ovok.com/errors/signals-tenant-not-own

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

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

The request needs the project to have a Signals tenant of its own, and this project uses the shared one. This covers calls to the Signals API through Ovok and making a Signals `manager` or `submitter` client application, since the shared tenant belongs to every project on it. Nothing was changed.

## Troubleshooting [#troubleshooting]

1. Check whether you are signed in to the project you meant. A sub-project created through Ovok has its own Signals tenant from the start.
2. Ask Ovok to move the project to a tenant of its own if it is an older one. A project that already has residents on the shared tenant stays on it until Ovok moves it.
3. Use a different kind of client application, such as one that needs no Signals tenant, if you only wanted to call Ovok's own API.

## Retry safely [#retry-safely]

Do not retry until the project has its own tenant. An unchanged request returns the same error. Nothing was created, so there is no client application to remove.

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