# TRACE NOT FOUND

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

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

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

No request event for this project has the supplied trace identifier. Clients should branch on `type` and `status`, not on human-readable `detail` text.

## Troubleshooting [#troubleshooting]

Check the ID, original response, timestamp and project that handled the request. Events can be project-scoped or outside retention. 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.

## Retry safely [#retry-safely]

Correct the request, configuration, access or project state described above before retrying. Repeating an unchanged request will normally return the same error; for writes, check whether the first attempt changed state before sending it again. 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 [#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](/errors) explains the response fields, while the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type audited for this release.