A form does not submit
Use this guide when pressing a form’s submit button leaves the visitor on the form, shows an error or completes without the expected follow-up action.
First identify the failing stage
Run one test with non-sensitive sample data and note the first visible response:
- A field-level message means validation stopped the submission.
- A form-level error can indicate consent, spam protection, an upload or another submission rule.
- A success message means the form was accepted; investigate its configured actions separately.
- No visible response suggests a page, script or stale-cache problem rather than a rejected field alone.
Check a rejected form
- Open Forms and edit the form used on the affected page.
- Review every required field and its field type.
- Check configured length, number, pattern and file limits against the sample value.
- Follow the same conditional path as the visitor. Hidden conditional fields are not validated, so a field that remains visible unexpectedly may still be required.
- Complete the configured privacy or consent field.
- Retest without browser autofill and with a permitted sample file if the form accepts uploads.
- Review spam-protection requirements and retry once without rapid repeated submissions.
Separate submission from delivery
When the success state appears, the form submission itself completed. Check the next action instead:
- For email, verify recipients, merge-tag values and mail delivery.
- For stored submissions, confirm that storage is enabled for this form.
- For webhooks or connected services, verify the action’s public configuration and required field mapping.
- For redirects, use a complete valid destination and test it after a successful submission.
Do not weaken validation or spam protection merely to make one test pass.
Check the page copy
If the form works in its editor or on a test page but not on the public URL:
- Confirm that the page embeds the current saved form.
- Update the page after replacing or reconfiguring the form.
- Purge page and CDN caches.
- Test while signed out in a private window.
The theme rebuilds the submission token required by its programmatic form flow, including on cached pages. A persistently old page copy can still serve obsolete surrounding markup or scripts.
Expected result
Valid input reaches the configured success state once, invalid input identifies a correctable field or rule, and each follow-up action is evaluated independently.