Guide · Updated May 2026
Markdown exportWhen the page flickers or shows a browser error
Client-side page errors can be caused by stale tabs, browser extensions, cached scripts, or temporary deployment changes.
What you may see
Use these points as the practical checks for this section.
- A brief layout flicker when the page loads
- A page error after clicking a button
- A browser console or support report mentioning hydration
- A Sentry or support reference to a client-side error
What this means
The browser had trouble matching the first page it received with the interactive page that loaded afterward, or a client-side script failed.
Historically, a known hydration mismatch caused brief page flicker. That issue has been fixed, but similar browser-side errors can still be caused by stale tabs, browser extensions, cached scripts, or temporary deployment changes.
What to do
Use these points as the practical checks for this section.
- Refresh the page.
- If the page is still broken, open it in a private window.
- Disable browser extensions that modify pages, translate content, block scripts, or inject password tools.
- Retry the action that failed.