# INVALID_NOTIFICATIONS

Canonical page: https://docs.ovok.com/errors/invalid-notifications

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

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

The omni-channel alerts rule, or a rule to preview, does not run: on at least one event type its logic fails, or answers something other than up to 10 `{ "notify": { "channels", "to" } }` entries. The message names the event it fails on. Nothing was saved.

## Troubleshooting [#troubleshooting]

1. Read the message for the event type and the entry that is wrong.
2. Check each entry has only `channels` and `to`, each a list of labels.
3. Try the rule with the preview route for that event before you save it again.

## Retry safely [#retry-safely]

Retry with a corrected rule. The same rule is refused every time. Nothing was saved, so the earlier rule still applies.

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