What you see when a diagnosis completes #
After you click Run Diagnosis and the capture and analysis complete, the Loupely Chrome extension popup updates to show your results. This happens in the same popup you opened to run the diagnosis: nothing opens in a new tab, nothing redirects you to a website. The result is right there in the extension.
Here’s what the popup contains and what each part means.
The diagnosis text #
The first thing you see is the diagnosis itself: 1 to 3 sentences in real human terms explaining what broke and where it came from. This is the output of the AI model working from Loupely’s correlation analysis. It’s specific to the failure pattern Loupely found in your capture, not a generic suggestion.
A typical diagnosis looks like:
- “A PHP Fatal Error in the WooCommerce Payments plugin fired during order processing. The error occurred in the Payment Gateway’s webhook handler and stopped the order record from being written to the database. The Payment Gateway processed the charge, but WooCommerce has no record of the order.”
- “A JavaScript error is preventing the checkout form from submitting. The error originates in a script loaded by your page builder and is caused by a naming conflict with a WooCommerce cart script loaded at the same priority.”
- “The REST API returned a 403 response to the checkout Ajax Request. A security plugin rule is blocking REST API requests that originate from the checkout page. The rule is treating the WooCommerce nonce verification request as a suspicious cross-origin call.”
If the diagnosis text is short or says something like “No clear failure pattern was identified in this capture,” see The Null Result: What It Means.
The triage step #
Below the diagnosis text is the triage: the specific next action to take. It’s tied directly to what the diagnosis found, not a generic checklist. See How Triage Recommendations Are Determined for a full breakdown of what each triage route means and how to act on it.
The triage step may include:
- the name of the specific plugin to deactivate or roll back
- the specific caching layer to clear
- language formatted for your hosting provider’s support team
- a pre-written message for developer handoff
The capture file download #
Below the triage is a button to download the structured capture file. This file contains the full sanitized diagnostic payload: every signal Loupely collected from the browser and the server, the correlation output, the failure classification, and the metadata about your site’s configuration at the time of capture.
You don’t need to download this file to act on the diagnosis and triage. It’s for 3 situations: you want to hand the problem to a developer who needs the full technical context, you want to upload it to an AI assistant for a deeper analysis, or you want to keep a record of what was happening at the time of a specific failure. See The Capture File: What’s in It and How to Use It for details on what’s inside.
The credit deduction #
A note in the popup confirms that 1 credit was consumed for this diagnosis (or indicates that the diagnosis ran against your annual plan). If you’re on credits, your updated balance is shown. This happens after the diagnosis returns successfully. If the diagnosis failed before completing, no credit is charged and the popup will indicate that.
Secondary options #
Some diagnoses surface a secondary option beneath the primary triage step: an AI handoff suggestion, a link to a relevant knowledge base article for the specific failure type, or a note about a related issue Loupely detected in the capture that didn’t rise to the level of the primary diagnosis but may be worth investigating. These are optional and contextual. Not every diagnosis includes them.
What the popup doesn’t show #
The popup doesn’t show raw PHP error text, stack traces, or the full capture file contents. Those are in the downloadable file. The popup is designed to give you the actionable information: what broke, why, and what to do. The raw evidence is there when you need it, but it’s not the first thing you see.