Emergency Use Only: Follow these procedures if a deployment causes critical issues.
Fast Recovery (Feature Flags)
Base44 Deployment Rollback
Base44 maintains deployment history. To rollback to a previous build:
Steps to Rollback:
- Open the Base44 dashboard for this app
- Navigate to Deployments or History section
- Locate the last known-good deployment (check build stamp and timestamp)
- Click Redeploy or Restore on that deployment
- Confirm the action
- Wait for redeployment to complete (usually 1-2 minutes)
- Verify the Build Stamp in console or Recovery page
Note: Base44 deployment details may be found in the platform dashboard under "Deployments" or "History". Contact Base44 support if rollback UI is not visible.
What Rollback Does and Does NOT Revert
✓ DOES Revert:
- Frontend code (pages, components, UI)
- Backend functions
- App logic and routing
✗ DOES NOT Revert:
- Database records (entity data is persistent)
- Database schema changes (new entities, fields remain)
- Environment variables / secrets
- User accounts and authentication data
- Stripe subscriptions or payment records
Important: If a deployment added new entity fields or entities, rolling back code will not remove them from the database. The app should handle missing/extra fields gracefully.
Emergency Checklist (Under Stress)
- Stay calm - you have recovery options
- Option A: Go to Feature Flags page → disable problematic feature
- Option B: Go to Base44 dashboard → find Deployments → restore previous build
- Check console for Build Stamp to verify which version is running
- Test critical paths: login, home page, subscription access
- Monitor for errors in browser console
- Document what went wrong for future reference
Build Information
Current Build Stamp:
2026-01-19-ROLLBACK-CHECK-01
2026-01-19-ROLLBACK-CHECK-01
This stamp is logged to console on app startup.
Use it to verify which deployment is currently running.
Use it to verify which deployment is currently running.
BUILD: 2026-01-19-ROLLBACK-CHECK-01