Read HTTP status, stable code, field details, request ID, and retry guidance.
How it works
Read HTTP status, stable code, field details, request ID, and retry guidance. TidyMessages keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.
Set it up
- Read the stable code, HTTP status, request ID, and affected resource.
- Classify the response as validation, permission, state, capacity, provider, media, or transient.
- 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.