---
title: "Understanding failed test runs"
description: "Use the run details panel and timeline to diagnose common failures and choose the next action."
translationKey: "troubleshooting-failed-test-runs"
tags: [troubleshooting, runs, diagnostics]
publishedAt: "2026-05-19"
lastReviewedAt: "2026-07-07"
indexable: true
faq:
  - question: "Where should I look first when a run fails?"
    answer: "Open run details and read the What went wrong panel first, then review timeline events and screenshots."
  - question: "Should I re-probe immediately after any failure?"
    answer: "Re-probe when fields, layout, or submit behavior changed. For temporary errors, retry first and compare timeline evidence."
---
> **Canonical:** https://formreceipt.com/docs/troubleshooting/understanding-failed-test-runs

# Investigate failed runs faster

When a run fails, start in run details. The "What went wrong" panel and timeline usually show enough evidence to pick a fix quickly.

## Step-by-step triage

1. Open the failed run.
2. Read the primary reason shown in "What went wrong".
3. Review screenshots and timeline events around submit and validation.
4. Apply the suggested next action and run a fresh test.

## Common reasons and what to do

- **Required field not completed:** update field mapping or probe again if the form changed.
- **Submit blocked or not triggered:** verify the visible submit control is still present.
- **Challenge or CAPTCHA shown:** automated checks cannot complete those challenges. During **Add form**, FormReceipt runs an access assessment: interstitials and HTTP blocks stop setup on step 1; CAPTCHA on the contact form itself saves as manual-only (no auto-setup). See [Allowlisting FormReceipt automation](/docs/troubleshooting/allowlisting-formreceipt-automation) when bot checks block runs repeatedly.
- **Page/plugin error:** inspect recent site changes, then retry after fixes.

## Re-probe vs retry

Retry first if nothing changed on the page. Re-probe if the form structure, fields, or plugin behavior changed.

## When to escalate

If repeated runs fail after updates, contact support with the run ID and a short summary of what changed on your site.