# VALIDATION_ERROR

Canonical page: https://docs.ovok.com/errors/validation-error

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/validation-error`](https://docs.ovok.com/errors/validation-error).

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

Signals read the request, but at least one value failed a check, so it changed nothing. `errors` lists one entry per invalid field. `data` carries the same failures in Signals' older shape.

## Troubleshooting [#troubleshooting]

1. Read `errors`. For each entry, `errors[].field` is the path to the value, `errors[].code` is the reason, such as `FIELD_REQUIRED` or `FIELD_INVALID_TYPE`, and `errors[].params` holds any limit.
2. Fix those values and keep the rest. Check required fields, types and enum values.
3. Send timestamps in ISO 8601, in UTC with a trailing `Z`.

## Retry safely [#retry-safely]

Fix the values and send the request once. Unchanged, it fails again. Signals changed nothing, so there is nothing to clean up.

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