> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.formstatus.co/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Test says the form failed, but it works fine for me

If FormStatus reports that a form test failed, but you can submit the form manually without problems, you’re not alone. There are a few common reasons why this might happen. Understanding these causes can help you troubleshoot quickly and ensure your forms are working reliably for all users.

### Common causes of false failures

${color}[#ff0000](javascript errors or conflicts) 

FormStatus simulates a real user visit to your site and attempts to submit the form just like a human would. If there are javascript errors on the page—such as issues from other plugins, broken scripts, or loading conflicts—the form may not behave correctly during automated testing.

* **Workaround: **check your browser’s developer console for javascript errors. Fixing these can often resolve the issue. Consider disabling unnecessary plugins or optimizing how scripts load on your site.

${color}[#ff0000](Captcha or anti-bot protection)
Some forms use Captcha, ReCaptcha, HCaptcha, or other types of anti-bot verification to block automated submissions. While these protect you from spam, they can also interfere with automated testing by blocking FormStatus from completing a submission.

* **Workaround: **for critical forms, you may want to add a "honeypot" spam trap instead of Captcha when possible. Alternatively, you can temporarily disable captcha for specific tests or work with your developer to create Captcha exceptions for trusted testing tools.

${color}[#ff0000](Browser differences)
FormStatus simulates form submissions using a headless browser that may not behave exactly like a regular browser you use every day. Differences in javascript execution, page rendering, or security settings can sometimes cause a form to behave differently in testing versus manual use.

* **Workaround: **ensure your form is designed to be browser-agnostic and free from dependencies on specific browser behavior. Testing forms in multiple browsers yourself (Chrome, Firefox, Safari) can also help catch inconsistencies.

${color}[#ff0000](Email delivery delays)
FormStatus checks if an email notification was successfully received after submitting a form. If your server’s email delivery is slow or delayed—especially on shared hosting—this could cause a test to fail even though the form submission itself worked.

* **Workaround:** review your site’s email setup. using an smtp plugin or external email service (like sendgrid, mailgun, or postmark) can greatly improve email reliability and speed.

### What to do if you encounter a test failure
* Manually test the form yourself to verify if users experience any problems
* Check for recent changes to the site, such as plugin updates or form setting adjustments
* Review the audit logs in FormStatus for more details about the failed test
* Investigate any potential javascript errors or captcha issues on the form page
* Monitor your site’s email delivery system if email delays are suspected

### Still seeing failures?
If you’ve gone through these checks and are still unsure why a form is failing, [reach out to our support team](mailto:support@formstatus.co). We’re happy to help review your setup and offer guidance to ensure your forms are running at their best.