Dashboard UX Lab

Scenario 5 of 6

Error with retry

The first request fails with a 503. Retrying recovers.

Try it in the lab

Expected behaviour

The server responds with a temporary failure. The dashboard explains it in plain language, shows a request ID, and offers Retry.

Why it behaves this way

Temporary failures are common and usually recoverable. A clear message and a single obvious action recover most sessions without support.

  • Say what failed and what the user can do, not just a status code.
  • Show a request ID people can quote to support.
  • Prevent double submissions while a retry is in flight.
  • If the control that had focus disappears, move focus somewhere meaningful.

Accessibility

The failure is announced. While retrying, focus stays on the Retry button; when it succeeds and the button disappears, focus moves to the dashboard heading so it is never lost.

Mistakes this scenario exposes

  • Retry buttons that can be triggered twice.
  • Focus dropping to the top of the page after a successful retry.