Triage is not a guess #
The triage step that appears after a Loupely diagnosis isn’t generated by asking an AI what you should do next. It’s determined by the correlation rules that classified the failure in the first place. The failure class drives the triage route. The AI explains the triage in context. The routing logic decides which path applies.
That distinction matters because it means the triage is tied to the specific evidence Loupely found, not to a general description of your problem.
The 5 triage routes #
Every Loupely diagnosis resolves to 1 of 5 triage routes. Here’s what each one means and when it applies.
1. Rollback #
Something changed recently and that change caused the failure. The triage step tells you what to roll back: a plugin update, a WordPress Core Update, a theme change, or a settings change. This route applies when the correlation rules find a clear before-and-after signal, such as a PHP error referencing a plugin file that was modified at a timestamp close to when the failure started.
Acting on a rollback triage: deactivate or downgrade the flagged plugin, or restore from a backup taken before the change. Loupely identifies what to roll back. How you execute the rollback depends on your hosting environment and whether you have a backup in place.
2. Plugin conflict #
2 or more active plugins are interfering with each other, producing failures that neither plugin would cause on its own. This route applies when Hook Execution data shows a conflict pattern, or when a JavaScript error references scripts from multiple plugins loading in a conflicting order.
Acting on a plugin conflict triage: deactivate plugins one at a time to isolate which pair is conflicting. Start with the plugins Loupely named in the diagnosis. The conflict triage often includes a specific test sequence to follow.
3. Hosting or server configuration #
The failure is rooted in your server environment rather than your WordPress installation. This applies when PHP memory limits, execution timeouts, server-level file permissions, or hosting configuration is causing failures that no amount of plugin management will fix.
Acting on a hosting triage: contact your hosting provider’s support. The diagnosis gives you specific language to use: the exact error, the likely server-side cause, and what you need your host to investigate or change. Most hosting providers can act on this information without you needing to understand the technical details yourself.
4. Cache clear #
A caching layer is serving stale content or interfering with dynamic functionality. This is a common cause of failures that appear after you’ve made a change that “should have fixed it” but didn’t seem to take effect. The route applies when the correlation rules find signs of cached responses conflicting with current server state.
Acting on a cache clear triage: clear your WordPress caching plugin’s cache, your CDN cache (if you use one), and your browser cache for the affected pages. The triage step specifies which caching layers are most likely involved based on what Loupely found.
5. Developer handoff #
The failure requires code-level investigation or a fix that can’t be achieved through settings changes alone. This is the most technically involved route. Loupely gives you a structured capture file and pre-written message formatted for developer handoff, so your developer has everything they need to diagnose and fix the problem without extended back-and-forth.
Acting on a developer handoff triage: download the capture file from the popup, copy the pre-written message, and send both to your developer. The message explains the failure in terms your developer can act on immediately, referencing the specific errors, hooks, and signals Loupely identified.
When triage includes an AI or support tool option #
Some diagnoses also surface a secondary option to use the capture file with an AI assistant or submit it to a support forum. This is always offered as an alternative to the primary triage route, not a replacement. The primary route is the one the correlation rules determined is most likely to resolve the problem. Use the AI or support option if the primary route doesn’t apply to your situation or if you want a second opinion before taking action.