TroubleshootingTroubleshooting1 min read
Troubleshoot access, 404 pages, and blank screens
Use a safe sequence to distinguish a wrong route, missing access, unpublished content, stale assets, and a deployment issue.
Version 1Last reviewed 23 Aug 2026
A 404 or blank screen does not always mean the record is deleted. The cause can be a misspelled URL, a protected module, an unpublished object, a missing relationship, a stale asset, or an incomplete deployment.
Start with the navigation entry instead of an old bookmark. Confirm you are signed in, have the required subscription or role, and are using the correct workspace. If the page belongs to a public site, confirm the profile, store, website, publication, or product is published.
Common questions
Why does a menu item exist when the page is unavailable? Navigation can expose a discoverable feature while the destination enforces the current account entitlement. What should I send support? The URL, account-safe context, time, browser, steps, and visible error—not credentials.
Steps
- Refresh the page and verify the route spelling.
- Open the module from the current sidebar or account menu.
- Check authentication, role, subscription, publication, and ownership requirements.
- Sign out and back in if navigation or assets appear stale.
- Open a ticket with the safe details if the issue persists.