COVERAGE_VERSION_MISMATCH
Coverage changed since read: what the COVERAGE_VERSION_MISMATCH error means and how to fix it.
HTTP 412. Problem type: https://docs.ovok.com/errors/coverage-version-mismatch.
What this means
The coverage changed since the version your If-Match header names, so your change was not applied over it.
Troubleshooting
- List the patient's coverages again and read the coverage's current
version. - Apply your change to what is there now, and send it with
If-Match: W/"<version>".
Retry safely
Sending the same If-Match fails again. Read the coverage first, then retry with its current version.
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