SIGNALS TENANT REVOKE FAILED

Troubleshoot signals tenant revoke failed responses from the Ovok API.

HTTP 502. Stable Problem Details type: https://docs.ovok.com/errors/signals-tenant-revoke-failed.

What this means

The child project was deleted but its Signals tenant could not be revoked. Clients should branch on type and status, not on human-readable detail text.

Troubleshooting

Treat deletion and tenant cleanup separately. Use traceId to inspect revocation state before retrying cleanup. Compare the request with the relevant endpoint's documentation and confirm the authenticated project and environment. Record the request path and traceId before escalating; the identifier lets an administrator find server-side context without sharing credentials or patient data.

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

Retry safely

For a 5xx response, wait for Retry-After when present and retry with bounded backoff. Before replaying a write, read the affected resource or operation state to avoid duplicate effects. Follow endpoint-specific idempotency and concurrency guidance. Do not retry in a tight loop or use a broader permission or project setting to bypass the check.

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 sensitive patient data from the report. The Error responses guide explains the response fields, while the machine-code registry lists every endpoint-specific type audited for this release.

Last updated on

On this page