# EPISODE_NOT_FOUND

Canonical page: https://docs.ovok.com/errors/episode-not-found

**HTTP 404.** Problem type: [`https://docs.ovok.com/errors/episode-not-found`](https://docs.ovok.com/errors/episode-not-found).

## What this means [#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 [#troubleshooting]

1. Check the episode ID. Take it from a list read with `episodes=true`, not from an alert: alert IDs are a different series.
2. Check `project`. It must match the project of the episode's patient.
3. Check that you are calling the environment where the episode opened.

## Retry safely [#retry-safely]

An unchanged request returns the same error. Nothing changed, so a corrected request is safe to send.

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