Glossary
Error state
What is an Error State?
An error state is what an interface shows when something goes wrong: invalid input, a failed request or a system problem. The message can help someone recover—or leave them wondering what to do next.
How it works
Good error feedback explains the known problem in plain language and gives a feasible next step. Put field-specific feedback near that field, preserve entered work where possible, and use more than color to draw attention to the problem.
Timing matters too. A form that announces an invalid email address while you are still typing it is interrupting you, not helping. Show feedback when the user can act on it.
Applied example
A payment form displays “Error 422: Unprocessable Entity.” That may be useful to the developer, but it leaves the customer stuck. If the system knows only that the payment was declined, a better message could be: “Your payment was declined. Please try a different payment method.”
The message should match the information available. Do not tell someone to fix a card number unless the system has identified that problem.
Why it matters
A failed action does not have to become an abandoned task. Clear feedback gives people a way forward, while preserving the work they have already done.