# EVENTS_NOT_IN_SCHEMA

Canonical page: https://docs.ovok.com/errors/events-not-in-schema

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/events-not-in-schema`](https://docs.ovok.com/errors/events-not-in-schema).

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

The subscriber names events that its event schema never sends, so Signals saved nothing. Each event schema version has its own event names, and a subscription to a name the schema does not send would receive nothing. A system subscriber receives patient events on event schema 2 only.

## Troubleshooting [#troubleshooting]

1. Read `detail`. It names the events the schema never sends.
2. Replace them with the schema's own event names, or set `eventSchema` to the version that sends them.

## Retry safely [#retry-safely]

Fix the events and send the request once. Unchanged, it fails again. Nothing was saved, 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.
