Appears when: Blank screen / app not loading
First separate a Base44 service incident from a project-specific failure. If the platform is healthy, capture the first browser error, identify the last working version, and test authentication, integrations, and the failing page without stacking more AI-generated changes.
# Preserve work during an outageDo not rewrite the app to compensate for an active platform incident.# Restore a known working versionUse the smallest rollback that returns a visible, testable application.# Reapply one isolated changeRepair the specific auth, integration, or runtime assumption with evidence.# Test the published pathVerify a clean load, login state, navigation, and the affected integration.Preserve the current working revision, change one proven boundary, and verify the published path in a clean session.
Confirm service status and whether another project or public page is affected.
What the result tells you: A current service incident changes the response: preserve work and avoid speculative project rewrites.
Record the change after which the page became blank and preserve that revision.
What the result tells you: A version-specific regression provides a small comparison surface.
Capture the first console and network failure, especially around auth or external services.
What the result tells you: A project-only exception or failed integration can be repaired without rebuilding the app.
| Likely cause | What proves it | First safe action |
|---|---|---|
| Temporary platform incident | A current service incident changes the response: preserve work and avoid speculative project rewrites. | Preserve work during an outage |
| Generated runtime regression | A version-specific regression provides a small comparison surface. | Restore a known working version |
| Authentication state failure | A project-only exception or failed integration can be repaired without rebuilding the app. | Reapply one isolated change |
| Broken external integration | A current service incident changes the response: preserve work and avoid speculative project rewrites. | Test the published path |
First separate a Base44 service incident from a project-specific failure. If the platform is healthy, capture the first browser error, identify the last working version, and test authentication, integrations, and the failing page without stacking more AI-generated changes.
The editor, runtime, or a shared service is unavailable beyond the project.
A recent change introduced an invalid state, component assumption, or navigation path.
The page waits on a user or permission state it never resolves.
Freeze generated changes, restore the last known working version, reproduce one request, collect the browser and platform logs, and change one layer at a time.
Check official status and compare another project or public page before changing project code or data.
Stop after the first unsuccessful broad fix. Preserve the last working version and diagnose the first concrete error.
Provide the affected URL, user state, first console or network error, last working version, and the last change made.
Free decision aid
Get a senior view of the constraint, the evidence you have, and the next decision that removes the most risk.
No email required for this decision aid. Dismiss once and this popup stays closed for the session.