Post-Update Breakage
Connect recent fatal errors, warnings, and pending updates to What Changed?, Error Log, Blast Radius, and Update Impact so you can identify the triggering change and understand its footprint.
What This Module Does
Recommended Diagnostic Paths analyses the evidence already available inside WP Health Inspector — including PHP error severity and source, autoload size, overdue cron events, pending updates, and database-related errors. It scores seven common WordPress problem scenarios and places the most relevant paths first.
Each recommendation explains which live signals caused it to appear, then presents the diagnostic modules to visit in order. The result is a practical investigation sequence tailored to the current site instead of a generic troubleshooting checklist.
Features at a Glance
Slow WordPress Admin
Use autoload thresholds, overdue cron counts, memory errors, and database signals to prioritise Autoload Governor, Cron Inspector, DB Health, Server & PHP, or Request Profiler.
Checkout & Payment Failures
Recognise WooCommerce file errors, HTTP or cURL failures, and Action Scheduler problems, then route the investigation through Error Log, Cron Inspector, External Dependencies, and Blast Radius.
Outages & White Screens
Prioritise fatal errors, memory exhaustion, execution-time failures, and overdue jobs when a site intermittently returns blank pages or HTTP 500 responses.
Plugin Conflicts
Detect evidence from multiple plugin paths, redeclaration errors, and update pressure, then move through Error Log and Blast Radius into the deeper Pro conflict and root-cause tools when available.
Database & Query Errors
Recognise WordPress database, wpdb, MySQL, missing-table, unknown-column, and SQL errors, then direct the investigation to Error Log, DB Health, Blast Radius, and Request Profiler.
Performance Regression
Use elevated cron volume, growing autoload payloads, deprecation notices, asset weight, and database size to build a focused performance investigation path.
Why It Matters
- Replaces random module-hopping with an evidence-based starting point
- Shows the exact live signals that made each scenario relevant
- Orders the recommended modules so each step adds context for the next
- Adapts automatically as errors, updates, cron status, and site conditions change
- Keeps diagnosis read-only while leaving every repair decision under administrator control
Frequently Asked Questions
How does WP Health Inspector choose a path?
Each scenario has weighted signals. The plugin evaluates current error-log findings, autoload size, cron status, pending updates, database errors, and related evidence, then sorts the paths by relevance score.
Does a recommendation prove that it found the cause?
No. A path identifies the most promising investigation sequence from the available evidence. The linked modules provide the detailed findings needed to confirm or rule out a cause.
Why do the recommendations change over time?
They are based on the site's current evidence. New errors, completed updates, changing cron backlogs, or a growing autoload payload can change which scenario deserves attention first.
Is this available in the free Lite version?
Yes. Recommended Diagnostic Paths is included in Lite and Pro. Some downstream analysis modules named by a path may require Pro.
Does following a path modify the site?
No. The path and its linked diagnostic modules inspect and explain the current state. They do not automatically repair, optimise, deactivate, or reconfigure the site.