Error Page 500
The 500 with a mono incident id, the team already paged, retry and status links.
The 500 with a mono incident id, the team already paged, retry and status links.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Error Page 500 is a full-page centered layout with no mascots and no whimsy. The heading states the facts plainly: something broke on our side. The request failed in our API, not in your browser, nothing you did caused it, and nothing was saved half done. A muted panel holds the incident ID inc_9f4k2d71 in mono with a copy button, labelled give support this, and explains it maps to the exact request and stack trace so support skips the back and forth. The one reassuring fact is stated plainly: the on call engineer was paged at the same moment you saw this page.
The incident ID is a const. The footer tells the user when to stop retrying: if retry fails twice, stop, the status page posts within minutes once confirmed.
Reach for this block as the destination for any unhandled 500 response, wired to your error boundary or server error handler so the incident ID is injected from the actual error event. The status page link should resolve to your real status subdomain.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the API failure page with an incident ID. Other server error pages:
Tip: no mascots on error pages, a broken robot is charming in a consumer app and off-putting in a product where something real just failed.