Troubleshooting
Formidable Forms Error Message: Causes and How to Fix It

Short answer
Formidable Forms shows an error when a field fails validation, a spam check blocks the entry, an entry limit flags a duplicate, a cached page serves an expired security token, or the server fails. Find which type it is, then fix the field rule, spam setting, cache exclusion or server problem behind it.
Key takeaways
- Field-level messages are set in each field's options in the form builder.
- Default form-wide messages live under Formidable Global Settings.
- Already submitted errors usually come from entry limits per user, IP or cookie.
- Errors only for logged-out visitors often point to cached pages and expired nonces.
- Upload errors come from field limits or server PHP upload settings.
Why does Formidable Forms show an error message?
Formidable Forms shows an error message when a field fails validation, a spam check blocks the entry, a duplicate is detected, a security token has expired, or the server returns an error during submission.
Most error messages are not bugs. They are Formidable doing its job, such as stopping an empty required field. The problem starts when a valid visitor sees an error, or when the wording is confusing.
This guide covers both cases: how to work out what a given error means, and how to fix or reword it.
| Error you see | Likely cause | Where to fix it |
|---|---|---|
| Errors are marked below on submission | A field failed validation | Field settings for that field |
| Already submitted message | Duplicate or limit check | Form settings and global messages |
| Entry flagged as spam | Honeypot, Akismet, captcha or blocklist | Spam settings and captcha keys |
| Generic error after a cached page | Expired security token (nonce) | Cache exclusion for the form page |
| Spinner then nothing, or a server error | PHP error or blocked request | Debug log and firewall |
| File upload error | File type, size or server limit | Field settings and PHP limits |
Which Formidable error messages come from field validation?
Validation errors appear under a field when it is required and empty, the value has the wrong format, or it fails a unique, length or pattern check you set.
Each field has its own validation settings in the form builder. Click the field and look at the options for required, unique values, format masks and min or max limits.
Typical validation causes:
- A required field left blank
- An email or URL field with an invalid value
- A phone or custom format mask that does not match what visitors type
- A unique setting that rejects a value already used in another entry
- A number field outside the minimum or maximum you set
If real visitors keep hitting the same error, the rule is probably too strict. Loosen the format, or add a helpful description under the field so people know what to enter.
How do you change the error message text?
Change field-level messages in each field's settings, and change form-wide default messages in Formidable's Global Settings, where you can edit the text shown for failed and duplicate entries.
Formidable lets you set custom text for the required message and the invalid message on each field. That is the best place to make errors specific, such as Please enter a work email address.
Global defaults live under Formidable > Global Settings. The Global Settings overview in the Formidable docs lists the message options and other site-wide settings.
Some messages can also be set per form in the form's settings. Check there first if you only want to change wording on one form. Our guide on how to use Formidable Forms Lite shows where the builder and settings screens are.
Why does Formidable say the entry was already submitted?
This message usually appears when the form limits entries per user, IP or cookie, or when the same submission is sent twice in quick succession.
Formidable can limit how many times someone submits a form. If that limit is on, a returning visitor sees the duplicate message even with new data.
Check these points:
- The form's settings for limiting entries per user, IP address or cookie
- Whether visitors share an IP, such as staff in one office
- A double click on the submit button sending two requests
- A browser autofill or back-button resubmission
If the limit is not needed, turn it off. If it is needed, use the logged-in user rather than IP, which avoids false blocks in shared offices.
Why are real entries being flagged as spam?
Real entries get flagged when a spam check such as the honeypot, Akismet, a captcha, a blocklist or the WordPress disallowed keys list decides the message looks like spam.
Formidable includes several layers of spam protection. Each one can produce a false positive.
Things to check:
- Captcha keys: wrong or expired reCAPTCHA, hCaptcha or Turnstile keys can fail every submission
- Script optimization: delaying captcha scripts can mean the token is missing on submit
- Akismet: test messages full of links or sales words often get flagged
- Disallowed keys: words in Settings > Discussion > Disallowed Comment Keys may also be checked by form plugins
Test with a plain, short message from a normal email address. The Google reCAPTCHA v3 docs explain how scores work if you use that option. Our guide on how to stop contact form spam in WordPress covers balanced settings.
What causes errors on cached pages?
Page caching can serve an old security token (nonce) with the form, so the submission fails or shows a generic error for visitors once that token expires.
WordPress nonces are valid for a limited time. When a cache plugin or host stores the form page for longer, visitors receive a stale token. The WordPress nonces documentation explains how they expire.
This problem has a clear pattern: the form works for you while logged in, but fails for visitors, often a day or so after the cache was built.
Fixes:
- Exclude pages with forms from page caching.
- Lower the cache lifespan below the nonce lifetime.
- Turn on AJAX submission for the form if available.
- Purge cache after changing form settings.
How do you find a server or JavaScript error behind the message?
Open the browser Network and Console tabs while submitting, then check the WordPress debug log, because a PHP error or blocked request often hides behind a vague error message.
If the form spins and then shows a generic error, or nothing, look for:
- A red error in the Console, often from another plugin's script
- A request returning 403, which suggests a firewall or security plugin block
- A request returning 500, which points to a PHP fatal error
Turn on logging by setting WP_DEBUG and WP_DEBUG_LOG in wp-config.php. The page on debugging in WordPress explains the constants. Our guide on how to read the WordPress debug log helps you find the right lines.
How do you fix file upload error messages?
File upload errors come from the allowed file types and size limit in the field settings, or from server limits such as upload_max_filesize and post_max_size.
First, open the file upload field and check the allowed types and maximum size. A visitor uploading a HEIC photo or a large PDF may hit those limits.
If the field limit is generous but uploads still fail, the server limit may be lower. The PHP manual describes upload_max_filesize and related settings. Your host can raise them, or you can change them in php.ini where allowed.
Also check that the uploads folder is writable. A permissions problem produces upload failures with little detail.
Could a plugin or theme conflict cause the error?
Yes, script optimization, security and page builder plugins can interfere with Formidable's scripts or requests, so run a conflict test if the cause is still unclear.
Use a staging copy and switch to a default theme. Then deactivate other plugins and test the form. Reactivate them one at a time until the error returns.
The Health Check and Troubleshooting plugin can do this for your session only, without affecting visitors.
Pay attention to cache plugins with delay JavaScript options, firewall plugins, and other form or captcha plugins loading their own scripts.
What if the form submits but emails do not arrive?
That is a separate problem: the entry is saved, but WordPress mail fails, so check your email actions and set up SMTP rather than changing error messages.
Look in Formidable > Entries. If the entry is there, the form worked. Delivery is the issue.
See our guide to Formidable Forms not sending email for the full fix list.
If you are still learning the plugin, what is Formidable Forms explains how forms, entries and actions fit together.
Before contacting Formidable support, note the exact error text, whether it happens only for logged-out visitors, and any console or log errors you found.
Frequently asked questions
How do I change the error message in Formidable Forms?
Edit field-level required and invalid messages in each field's settings in the form builder. Change form-wide default messages, such as the duplicate entry text, under Formidable Global Settings or the individual form's settings.
Why does my Formidable form say errors are marked below when nothing is marked?
A hidden field, a field on another page, or a field hidden by conditional logic may still be failing validation. A spam or captcha check can also fail without marking a field. Check required hidden fields and captcha settings.
Why does Formidable work for me but not for visitors?
Logged-in users usually bypass page caching. Visitors may get a cached page with an expired security token, which makes the submission fail. Exclude form pages from caching and purge the cache.
Can I turn off the duplicate entry check?
If the error comes from an entry limit, you can turn that limit off in the form's settings. If you need a limit, base it on logged-in users instead of IP address to avoid blocking people on shared networks.
Do Formidable error messages affect saved entries?
A submission that fails validation or spam checks is normally not saved as a regular entry. Once the error is fixed and the form submits, the entry appears under the plugin's entries screen.
Sources
- Global Settings Overview Formidable Forms
- Nonces WordPress Developer Resources
- Debugging in WordPress WordPress Developer Resources
- Core php.ini directives PHP Manual
- reCAPTCHA v3 Google for Developers
- Health Check and Troubleshooting WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


