Skip to content
FormReceipt

Troubleshooting

Understanding failed test runs

Use the run details panel and timeline to diagnose common failures and choose the next action.

Published: 2026-05-19Last reviewed: 2026-05-19

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.
  • Page/plugin error: inspect recent site changes, then retry after fixes.

If anti-bot protection is causing repeated challenge failures, follow Allowlisting FormReceipt automation.

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.

FAQ

Where should I look first when a run fails?
Open run details and read the What went wrong panel first, then review timeline events and screenshots.
Should I re-probe immediately after any failure?
Re-probe when fields, layout, or submit behavior changed. For temporary errors, retry first and compare timeline evidence.

← TroubleshootingKnowledge base home← Back to home

Cookie choices

We use a required session cookie for login and optional analytics cookies for marketing pages. Read cookie policy