EPISODE_NOT_FOUND
Episode not found: what the EPISODE_NOT_FOUND error means and how to fix it.
HTTP 404. Problem type: https://docs.ovok.com/errors/episode-not-found.
What this means
Signals has no episode with that ID that you may see. Either the episode does not exist in the tenant, or its patient is not in the project you sent. Both answer the same way, so the error reveals nothing about IDs outside your scope. Nothing changed.
Troubleshooting
- Check the episode ID. Take it from a list read with
episodes=true, not from an alert: alert IDs are a different series. - Check
project. It must match the project of the episode's patient. - Check that you are calling the environment where the episode opened.
Retry safely
An unchanged request returns the same error. Nothing changed, so a corrected request is safe to send.
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