Troubleshooting
A practical order for diagnosing the common problems before resorting to manual file changes.
Start with the evidence Micro CMS already records. Randomly replacing files or clearing recovery markers usually makes the real problem harder to identify.
1. Run the built-in checks
Open Site Health and Diagnostics. Fix the first concrete failure or warning related to the feature you are testing.
2. Check Background Jobs
If mail, migration, scheduled publishing or another queued task is not moving, open Background Jobs. A due job that remains at attempt 0 usually means the worker or scheduler did not run.
3. Check package integrity
If an Extension or Resource Pack suddenly becomes untrusted after a file edit, compare it with the signed release. Do not edit installed signed package files in place.
4. Check routes after a move
If Admin works but public routes do not, verify the configured public/control bases and the web-server rewrite/forwarding rules. Do not assume the physical directory should match the public address.
5. Check update recovery state
If the site is still locked after an interrupted Core update, use the update recovery page. Keep the recovery marker and rollback files until recovery is complete.
6. Bridge-specific checks
Use Bridge Health to check the selected Silos, then review the status shown for the Host operation. For normal site jobs, use that Silo’s Background Jobs screen.