Auto-repair playbooks.
Pre-approved actions that Care can take automatically when a known failure pattern is detected. Every action is logged in full. You approve each playbook — Care never acts without your permission.
01 / How it works
You approve each playbook
Playbooks are not enabled by default. In Settings > Automation, you see every available playbook with a description of exactly what it does. You enable only the ones you are comfortable with. Care never runs an action you have not approved.
02 / How it works
Care detects the failure pattern
When a monitored path fails its assertion, Care matches the failure signature against enabled playbooks. If a match is found and the playbook is allow-listed for this site, Care queues the playbook run.
03 / How it works
Every step is logged
Care logs every action taken: what command was run, what it returned, and what the path status was before and after. The full log is visible in Portfolio > your site > Playbook runs.
04 / How it works
Reversible actions can be undone
Playbooks marked reversible can be rolled back from the dashboard. For example, a disabled plugin can be re-enabled with one click, or a rolled-back deployment can be re-deployed.
05 / How it works
You are notified before and after
Care sends a notification when it begins a playbook run (so you are never surprised) and another when it completes, with a plain-English summary of what was done and whether the path recovered.
Playbook catalogue
Available playbooks
Cache flush
Trigger: Stale response body after a deploy
Action: Purges object cache (Redis / Memcached) and CDN edge cache layer.
Plugin conflict isolation
Trigger: 500 or 503 on a page known to be stable pre-update
Action: Renames the most recently activated plugin folder to disable it, then re-tests the failing path.
PHP error log retrieval
Trigger: 5xx on checkout or cart
Action: Fetches the last 200 lines of the PHP error log and attaches them to the incident for diagnosis.
SSL renewal trigger
Trigger: SSL certificate expiry within 7 days
Action: Triggers a Let's Encrypt renewal via the hosting provider API and verifies the new certificate.
Deployment rollback
Trigger: Error rate spike within 10 minutes of a deploy
Action: Rolls back to the previous successful deployment on Vercel, Netlify, or via SSH for VPS hosts.
DB connection reset
Trigger: Persistent 500s with MySQL/Postgres connection errors in the error log
Action: Restarts the PHP-FPM pool or flushes the persistent connection pool to reset stale DB connections.
Enable auto-repair for your site.
Add your site to Liulum Care and allow-list the playbooks that fit your stack.