# DUPLICATE_READING

Canonical page: https://docs.ovok.com/errors/duplicate-reading

**HTTP 409.** Problem type: [`https://docs.ovok.com/errors/duplicate-reading`](https://docs.ovok.com/errors/duplicate-reading).

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

Signals already stored this reading, so it neither stored nor evaluated it again. A reading counts as the same when its observation time, code, device and own `refId` match a stored one. `data.observationId` names the stored reading.

## Troubleshooting [#troubleshooting]

1. If you resent the reading after a timeout or a lost response, treat this as success: the first attempt was stored. `data.observationId` is its ID.
2. If the readings really differ, give each its own observation time or identifier.
3. Check that your sender does not send each reading twice.

## Retry safely [#retry-safely]

Do not retry. The reading is stored and was evaluated once. Resending it returns the same error and changes nothing.

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