What a Null Result is #
A Null Result is what you get when Loupely completes a capture and analysis but can’t identify a clear failure pattern from the signals it found. The popup might say something like “No clear failure pattern was identified in this capture” or return a very low-confidence classification. No credit is charged for a genuine Null Result where the diagnosis pipeline failed to return a result.
A Null Result is not an error. It’s an honest answer: Loupely looked at the available evidence and couldn’t find a pattern that maps to a known failure class with enough confidence to name a cause. That’s worth understanding, because it tells you something useful about what to do next.
Why null results happen #
The failure didn’t produce signals during the capture window. If the problem is intermittent and didn’t occur while Loupely was capturing, the evidence isn’t there. The browser buffer captures 60 seconds of activity, but if the failure happened 5 minutes ago and hasn’t recurred, there’s nothing to correlate. The fix: reproduce the failure deliberately and run the diagnosis again immediately after.
The failure lives in a layer Loupely doesn’t instrument. Loupely captures browser signals and WordPress server signals. It doesn’t reach into your Payment Gateway’s external servers, your CDN’s origin configuration, your DNS provider, or your Email Delivery service. A failure that lives entirely outside WordPress (a Stripe webhook misconfiguration, a Mailchimp integration timing out, an SPF record causing email rejection) won’t produce WordPress-level signals for Loupely to find.
The failure is at the database level. Loupely captures WooCommerce pipeline events and PHP Errors, but deep database integrity issues, corrupted tables, or Database Connection failures that don’t produce PHP Errors may not generate signals Loupely can correlate. Your hosting provider’s database tools are the right layer for these.
The page was in a recovered state. WordPress’s recovery mode and some security plugins actively suppress error output, which means the signals that would normally appear in a PHP error log or REST API response aren’t present during the capture. If your site is in recovery mode or has aggressive error suppression active, Loupely may find a clean picture that doesn’t reflect the actual failure state.
The failure is too novel for current correlation rules. Loupely’s correlation rules cover known failure patterns. A genuinely novel combination of plugins, a custom-built feature, or an edge case in a recent plugin update may produce signals that don’t match any existing pattern. The capture file still contains the raw evidence, which a developer can use even when the automated correlation doesn’t find a match.
What to do after a Null Result #
- Reproduce and recapture. If you got a Null Result because the failure wasn’t active during the capture, reproduce the failure and run the diagnosis again immediately. Trigger the broken action (submit the form, click checkout, do whatever causes the problem) without navigating away, then click Run Diagnosis within 60 seconds.
- Check browser-only signals. Even when correlation finds no pattern, you can download the capture file and look at the browser signals section. A developer can often spot something useful in the raw JavaScript errors or network requests even when the automated analysis doesn’t produce a classification.
- Download the capture file and hand it to a developer. A Null Result doesn’t mean the capture is empty. It means the automated pattern matching didn’t find a match. The developer handoff route is always available regardless of whether a diagnosis was produced. A developer with the capture file has significantly more to work from than a description of symptoms.
- Check your hosting provider’s logs. For database failures and server-level issues outside WordPress’s error reporting, your hosting control panel’s error logs often contain information that isn’t available to Loupely’s WordPress Plugin layer.