ALERT_NOT_FOUND

Alert not found: what the ALERT_NOT_FOUND error means and how to fix it.

HTTP 404. Problem type: https://docs.ovok.com/errors/alert-not-found.

What this means

Signals has no alert with that ID that you may see. Either the alert 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

  1. Check the alert ID. Take it from a row of the alert list, not from an episode: episode IDs are a different series.
  2. Check project. It must match the project of the alert's patient.
  3. Check that you are calling the environment where the alert was raised.

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

On this page