# SETTINGS_TOO_LARGE

Canonical page: https://docs.ovok.com/errors/settings-too-large

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/settings-too-large`](https://docs.ovok.com/errors/settings-too-large).

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

The settings would be larger than 64 KiB after the write, so Signals saved nothing. A write merges into the stored settings, so a small write can still push the whole document over the limit.

## Troubleshooting [#troubleshooting]

1. Read the stored settings and measure them together with your change.
2. Remove keys that are no longer used, such as triggers for codes you do not measure.
3. Move settings that only some patients need from the organization's settings to those patients' own settings.

## Retry safely [#retry-safely]

Shrink the settings and send the write once. Unchanged, it fails again. Nothing was saved.

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