Recover from a blank page or 404
Use symptom-first checks for missing routes, stale assets, permissions, and incomplete deployment state.
A blank page or 404 can come from an incorrect route, missing subscription, stale cached assets, an unpublished record, or an incomplete deployment. Start with the page URL and account access rather than changing application files.
Steps
- Refresh the page and confirm the URL is spelled correctly.
- Check whether the page requires a subscription or administrator permission.
- Try the module entry point and verify the record is published or active.
- Sign out and back in if navigation appears stale.
- If the issue remains, submit the URL, safe steps, and reference number to support.
Was this guide helpful?
Ask for help