# NOTIFICATION_NOT_FOUND

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

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

## What this means [#what-this-means]

No notification with this ID is visible to you, so Ovok did not mark it as read. Ovok gives the same answer when the notification never existed, belongs to another project or person, or is older than 90 days.

## Troubleshooting [#troubleshooting]

1. Check the ID. Use the `id` from your notification list, not an ID from another system.
2. Check the project and account. You see only notifications of the project in your session that are addressed to you, or to admins when you are an admin. A token for another project or user gets this answer.
3. Check the age. Notifications older than 90 days are hidden at once and deleted later. List your notifications again and use a current ID.

## Retry safely [#retry-safely]

Do not retry the same ID, because it gets the same answer. List your notifications and mark a current one as read. Nothing was changed.

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