SIGNALS_TENANT_NOT_OWN

Signals tenant not the project's own: what the SIGNALS_TENANT_NOT_OWN error means and how to fix it.

HTTP 409. Problem type: https://docs.ovok.com/errors/signals-tenant-not-own.

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

  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

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

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 explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page