Troubleshooting
Gravity Forms Not Working: Causes and How to Fix It

Short answer
Gravity Forms usually stops working because of a JavaScript error, a plugin or theme conflict, caching or script optimization, an outdated version, or a server limit. Check Forms > System Status first, clear caches, look for browser console errors, then test for conflicts on a staging copy.
Key takeaways
- Identify the exact symptom first, since a missing form and a failed submission have different causes.
- The System Status page shows versions, environment warnings and incomplete upgrades in one place.
- Script optimization features and Cloudflare Rocket Loader often break form submissions.
- Test conflicts safely with the Health Check plugin's troubleshooting mode or a staging site.
- Entries saved without emails point to mail delivery, not to the form itself.
Why is Gravity Forms not working?
Gravity Forms usually stops working because of a JavaScript error, a plugin or theme conflict, caching, an outdated version, a server limit, or a form that is inactive or embedded with the wrong ID.
Not working can mean several different things. The form may not appear, the submit button may spin forever, entries may not save, or emails may not arrive. Each one has its own likely causes.
Start by writing down exactly what happens and on which page. Then match it to the sections below. That saves time compared with switching plugins off at random.
| Symptom | Most likely causes |
|---|---|
| Form does not appear | Inactive form, wrong form ID, missing theme hooks, JavaScript error |
| Submit button spins or does nothing | JavaScript conflict, caching, AJAX blocked by security rules |
| Error after submitting | Validation, reCAPTCHA, file upload limits, server errors |
| Entry saved but no email | Mail delivery problems, notification settings |
| Conditional logic not working | JavaScript errors, delayed scripts |
How do you check the Gravity Forms System Status?
Go to Forms > System Status to see your Gravity Forms version, WordPress and PHP versions, active plugins, theme, and any database or environment warnings.
The System Status page is the best first stop. It flags outdated versions and missing database tables in one place. If an upgrade did not finish, it usually tells you.
Note the PHP version shown there. Very old PHP versions can cause errors with current releases. Our guide on which PHP version to use for WordPress explains how to check what your host offers.
Look for warnings about the database version or missing tables too. Gravity Forms stores forms and entries in its own tables, and an interrupted upgrade can leave them out of date. The System Status page usually offers a button to finish or repair the upgrade.
Also update Gravity Forms and its add-ons from the Plugins screen. Your license must be active for automatic updates. The Gravity Forms documentation lists current requirements.
Why is your form not showing on the page?
A form usually fails to show because it is inactive, the block or shortcode points to the wrong form ID, the page is served from an old cache, or a JavaScript error stops it from rendering.
Check these in order:
- Go to Forms and confirm the form is set to active
- Edit the page and confirm the Gravity Forms block or shortcode uses the correct form
- Open the page in a private window to bypass logged-in caching
- Clear your page, plugin and CDN caches
- Open the browser console and look for red errors
If the form shows in the block editor preview but not on the live page, caching or script optimization is the likely cause.
Some page builders and custom themes do not output the standard WordPress footer hook. Gravity Forms relies on scripts loaded there, so a theme that skips it can break forms. Switching briefly to a default theme confirms this.
Page builders can also cause trouble when the form sits inside a popup, tab or slider that loads after the page. In that case the form scripts may run before the form exists. Placing the form directly on the page is a quick way to check this.
Why does the submit button spin or do nothing?
A spinning or dead submit button usually points to a JavaScript conflict, a delayed or combined script, or a firewall rule blocking the AJAX request that sends the form.
Open the browser's developer tools before clicking submit. The Console tab shows script errors, and the Network tab shows whether the submission request returns an error code. The MDN guide to developer tools explains both tabs.
Common fixes include:
- Excluding Gravity Forms and jQuery from delay JavaScript and combine JavaScript features
- Turning off Cloudflare Rocket Loader for the form page
- Asking your host to check firewall or ModSecurity logs for blocked requests
- Disabling AJAX on the form temporarily to see if a normal submit works
If you use an optimization plugin, our guide on how to clear cache in WordPress helps make sure you are testing fresh files after each change.
How do you test for a plugin or theme conflict?
Test on a staging copy by switching to a default theme and deactivating other plugins, then re-enable them one at a time until the form breaks again.
Conflicts are the most common cause of strange form behaviour. Another plugin may load an old jQuery version, a different reCAPTCHA script, or code that changes form markup.
The safest way to test is the Health Check & Troubleshooting plugin. Its troubleshooting mode disables plugins and switches theme only for your own session, so visitors see the normal site. See the Health Check plugin page for details.
Our step-by-step guide to fixing plugin conflicts walks through the full process. Once you find the plugin causing trouble, check for an update or contact its developer with the details.
Why do you see an error after submitting?
Errors after submitting usually come from validation rules, CAPTCHA checks, file upload limits, or a server error, and the message or log tells you which one.
There was a problem with your submission means at least one field failed validation. Scroll through the form; the failed field is highlighted with its own message.
If the problem involves CAPTCHA, our guide to Gravity Forms reCAPTCHA not working covers keys, domains and script conflicts.
File upload fields fail when files exceed the field limit or the server's upload limit. The server limit is set by PHP's upload_max_filesize and post_max_size values, described in the PHP manual. Your host can raise them.
A blank page, a 500 error or a critical error message points to a PHP problem. Turn on WordPress debug logging, submit again, and read the log.
Why are entries saved but emails not sent?
If entries appear under Forms > Entries but no email arrives, the form works and the problem is email delivery or the notification settings.
WordPress sends mail through the server by default, and many hosts handle that poorly. Messages are often blocked or land in spam. An SMTP plugin that sends through a proper mail service fixes most cases.
Also check that the notification is active, has the right recipient, and has no conditional logic stopping it. Our full guide to Gravity Forms notifications not sending walks through each check.
How do you use Gravity Forms logging?
Turn on logging under Forms > Settings, reproduce the problem, then open the log for Gravity Forms core or the relevant add-on to see what happened step by step.
Logs record what happens during each submission, including validation results, notification sending and add-on feeds such as payment or email marketing connections. They often show the exact failing step.
The logging and debugging guide explains how to enable it and where logs are stored. Turn logging off when you are done, since logs can contain personal data from form entries.
When should you contact Gravity Forms support?
Contact support once you have updated everything, ruled out conflicts and caching, and collected your System Status report and logs showing the error.
Support can only help quickly with clear details. Include the System Status report, the form export, the steps to reproduce the problem, and any log lines or console errors.
If the issue started after an update, mention the version numbers. You can roll back a plugin update as a temporary fix while you wait, but keep the rollback short for security reasons.
Prevent repeat problems by testing form submissions after every plugin, theme or WordPress update. A quick test entry takes a minute and catches most breakages early.
Frequently asked questions
Why does my Gravity Forms form not show up?
The form may be inactive, the block or shortcode may use the wrong form ID, or the page may be cached. A JavaScript error or a theme that skips the standard footer hook can also stop it rendering. Check the form status, the embed, and the browser console in that order.
Why does the Gravity Forms submit button keep spinning?
A spinning button usually means the AJAX submission failed. Common causes are JavaScript conflicts, script delay or combine features in optimization plugins, and firewall rules that block the request. Check the browser console and network tab, then exclude Gravity Forms scripts from optimization.
Can a caching plugin break Gravity Forms?
Yes. Page caching can serve outdated form markup, and features that delay or combine JavaScript can stop the form scripts running. Exclude Gravity Forms pages or scripts from those features and purge all caches after changing settings.
Where do I find Gravity Forms error logs?
Enable logging in the Gravity Forms settings, reproduce the problem, then view the logs from the logging section of the settings or System Status page. For PHP errors, also enable WordPress debug logging and check the debug log file in the content folder.
Does Gravity Forms stop working if my license expires?
Existing forms keep working after a license expires, but you stop receiving updates and support. Over time, missing updates can cause compatibility problems with newer WordPress or PHP versions, so renewing or replacing the plugin before that happens is the safer path.
Sources
- Gravity Forms Documentation Gravity Forms
- Logging and Debugging Gravity Forms
- Health Check & Troubleshooting WordPress.org
- Debugging in WordPress WordPress Developer Resources
- Core php.ini directives PHP Manual
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.


