---
title: "1xxx validation errors"
description: "Resolve missing, malformed, conflicting, oversized, unknown, or unsupported input."
image: "https://help.tidymessages.com/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tidymessages.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 1xxx validation errors

Resolve missing, malformed, conflicting, oversized, unknown, or unsupported input.

## How it works

Resolve missing, malformed, conflicting, oversized, unknown, or unsupported input. TidyMessages keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.

## Set it up

1. Read the stable code, HTTP status, request ID, and affected resource.
2. Classify the response as validation, permission, state, capacity, provider, media, or transient.
3. Correct permanent failures or retry transient failures with bounded backoff and the original Idempotency-Key.

## What to expect

- The operation is traceable by stable request and resource identifiers.
- Acceptance, provider delivery, and customer interaction remain separate states.
- Retries and reordered events do not duplicate the customer action.
> [!TIP] Apply retry budgets per resource; never replay an entire failed queue at once.

Source: https://help.tidymessages.com/errors/1xxx-validation-errors/index.mdx