Server Error 500

About this block

Server Error 500 takes the blame correctly. The ghosted code, a headline that owns it, this one is on us, and a body that answers the three panic questions in order, we know, your data is safe, your draft survived. Try again and the status page are the actions, and the footnote gives an error ID that skips the support triage queue.

The copy is strings, and the error ID should interpolate from your real error tracking at integration. The drafts save as you type line must be true of your product before this page can say it.

When to use

Reach for this block as the app and site 500 page. Error pages are read in the worst mood a user has, every sentence exists to lower heart rates. The status link pairs with current-status-list, an error page pointing at a live status page is the system working even while it fails.

A natural flow around it on a Marketing Pro page:

Before

• Navbars kept functional so escape routes exist

After

• Footers with the support links intact

What you can display

One strong use is the application 500. Other failures:

• Payment failure. The checkout error with the card not charged reassurance leading.
• Timeout page. Long operations that gave up, with the result will email you promise.
• Rate limited. The slow down page for API consumers, with the retry math shown.

Tip: the error ID footnote converts the angriest users into the best bug reports, wire it to real tracking.