2 min read
A fatal error in a plugin can white-screen a site in seconds. XPulse includes a fatal error catcher that detects crashes, keeps the site online, and notifies the team: turning a potential outage into a logged incident.
| Alert | Meaning |
|---|---|
| Auto-Healed Fatal Crash (critical) | A fatal error was caught and the offending plugin was auto-deactivated to keep the site live |
| Plugin Crash Logged (warning) | A plugin crashed but the site stayed online: the crash was logged for review |
This is the difference between a 5-minute contained incident and a down site.
Each logged crash records:
– Which plugin threw the error
– The error message and file/line
– When it happened
– The page/context where it occurred
wp eval 'print_r(json_decode(get_option("xpulse_crash_log", "[]"), true));'
| State | What happens next |
|---|---|
| Auto-healed | The plugin stays deactivated until it’s safe. We review the log, check for an update/fix, and re-enable only when safe: or recommend a replacement |
| Logged only | Site stayed up. We review and monitor; if it recurs we escalate to deactivation or replacement |
Crash events can push to a webhook (Slack, Discord, or your monitoring stack) so your team hears about incidents even outside the dashboard. Request webhook setup via support.
