Skip to content

fix(ui): Update route error page with troubleshooting guide and support instructions#110687

Merged
nora-shap merged 2 commits intomasterfrom
nora/update-routeError-links
Mar 16, 2026
Merged

fix(ui): Update route error page with troubleshooting guide and support instructions#110687
nora-shap merged 2 commits intomasterfrom
nora/update-routeError-links

Conversation

@nora-shap
Copy link
Member

The route error page previously linked users to open a GitHub issue when something went wrong. This replaces that with more actionable guidance:

  • Links to the Zendesk troubleshooting guide for common browser-related issues
  • Adds a support contact section with a checklist of useful diagnostic details to include (browser logs, affected users, browser/version, consistency, affected URLs)
  • Fulfills the existing (10year old 😅 ) TODO to show additional resource links

NOTE: I used inline styles on purpose - this is the error page that must render when CSS/JS bundles fail to load, so I wanted the formatting degrade gracefully.

before
Screenshot 2026-03-13 at 1 15 10 PM

after
Screenshot 2026-03-13 at 2 01 17 PM

@nora-shap nora-shap requested a review from thetruecpaul March 13, 2026 21:23
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 13, 2026
@nora-shap nora-shap requested a review from a team March 16, 2026 20:12
`)}
</p>
<p>{t("If you're daring, you may want to try the following:")}</p>
<p style={{marginBottom: 0}}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure you want marginBottom: 0 here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

purely visual - it balances the appearance of the <p>s with the <List>s

)}
</ListItem>
</List>
<p style={{marginTop: '1em', marginBottom: 0}}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comment

`Still stuck? Our [link:troubleshooting guide] has tips for common browser-related issues.`,
{
link: (
<ExternalLink href="https://sentry.zendesk.com/hc/en-us/articles/22088541158555-Why-Sentry-io-is-not-loading" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this make sense to show for self hosted

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, this is basic browser/plugin troubleshooting

{
link: (
<ExternalLink href="https://github.com/getsentry/sentry/issues/new/choose" />
<ExternalLink href="https://sentry.zendesk.com/hc/en-us/requests/new" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same question here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updating this to a more generic support page that both sh and saas can use 👍

@nora-shap nora-shap merged commit 4ffafba into master Mar 16, 2026
63 checks passed
@nora-shap nora-shap deleted the nora/update-routeError-links branch March 16, 2026 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants