Database Backoff Schedule Error Block for React

No. An attempt waits 600 ms behind a spinner and is then refused, with the error typed in the file (ECONNREFUSED, against a documentation address), so a viewer can run the whole schedule without anything happening. To wire it, open your connection where the code says so, keep the busy state until it answers, and on success take the person to the page they wanted; keep the schedule and the refusal text for failures.

Never on load. It starts when the visitor turns Retry automatically on, runs for one gap, makes the attempt and starts the next gap, so at most five waits (62 seconds in all) and one timer at a time. Turning the switch off stops it, Retry now skips the rest of a wait, and after the fifth attempt the switch turns off by itself. A screen reader hears a sentence ("8 seconds until the next attempt") instead of the digits, and with reduced motion the ticking digits are replaced by the length of the wait.

Edit GAPS, in seconds. The segments are drawn in proportion to them, the total and the count of attempts are derived, and the cells under the bar follow. Exponential backoff doubles the wait up to a ceiling; adding jitter in your client stops many clients retrying in the same second, which a typed schedule can't show.

By the fill and the word: a solid segment and "Refused" for an attempt made, an outlined segment and "Next" for the one that is coming, a dashed segment and "Waiting" for the rest. The weight of the words follows the same order. The page uses no status color.

Tab reaches Retry now and the switch. A busy button disables itself, which drops keyboard focus, so when an attempt you started ends, focus moves to the result line, which is a polite status message ("Attempt 2 of 5 refused. The next one waits 8 seconds."). Attempts that the timer starts speak the same line without moving focus.

A 503, with a Retry-After header when you have an honest estimate, so browsers and monitoring treat it as an outage and not as content. The page can't set it; your server or framework does. Don't show hostnames, credentials or the connection string, which is why the cells show counts only.