| Previous | Next |
| ERROR_STATE_COMPOSITE_SETTING_VALUE_SIZE_LIMIT_EXCEEDED | ERROR_STATE_SETTING_NAME_SIZE_LIMIT_EXCEEDED |
ERROR_STATE_SETTING_VALUE_SIZE_LIMIT_EXCEEDED
The setting value is too large
ERROR_STATE_SETTING_VALUE_SIZE_LIMIT_EXCEEDED means one value is larger than the state repository permits. This is deterministic for the same serialized payload.
How to fix it
- Measure the encoded size rather than the source object size.
- Use a smaller representation for configuration data.
- Move large text, media, or cache data to an appropriate file store.
- Keep only identifiers, paths, or compact metadata in the setting.
Application behavior
Leave the previous persisted value intact and tell the caller that the new value was not saved. Automatic truncation is dangerous because it can produce syntactically valid but semantically corrupted data.
Encoding matters
A value that appears small as characters or an in-memory object may expand after UTF encoding, metadata, or serialization. Validate the exact byte representation passed to the API.
User-facing behavior
Explain that the value is too large and preserve the previously saved setting. Do not truncate silently, because a shortened path, token, JSON document, or regular expression may remain valid while changing meaning.
References
Looking for a different code? Search another status or error code.