You built a form with Forminator. Everything worked fine. Then one day, users started seeing “Something went wrong” or “Form submission failed.” No email arrives. No confirmation shows. That is frustrating because the form looks normal but does not work.
A common issue is that site owners blame the plugin or hosting. But the real problem is often a timeout, a server limit, or a conflict with another tool. Forminator is showing you the error message. The question is what triggers it.
Why AJAX Forms Fail Without Clear Reasons
Forminator uses AJAX to submit forms without reloading the page. That creates a smooth experience but also introduces more points of failure. The browser sends data in the background, waits for a response, and then shows the result. If anything interrupts that process, you get a generic error.
This is not Forminator being broken. This is the AJAX request failing somewhere between the browser and your server.
The Most Common Causes of “Something Went Wrong”
- PHP max execution time is too low
- Memory limit is exhausted during form processing
- File uploads exceed server limits
- A security plugin blocks the AJAX request
- A caching plugin caches the form submission URL
- Forminator nonce (security token) expires
Any of these can break the form without changing any Forminator settings.
Why Timeout Is Usually the Real Problem
If your form sends emails, saves entries, or integrates with external services like Brevo or Fluent CRM, processing takes time. If your server cuts off the request after 30 seconds, the AJAX call fails.
Forminator waits for a response. If no response comes in time, it shows “Something went wrong” even though the form actually processed correctly on the server side.
How to Find the Real Cause
- Open browser developer tools (F12) → Network tab
- Submit the form and watch the AJAX request
- Look for HTTP error codes like 500, 403, or 408
- Check PHP error log on your server
- Check Forminator submission log if enabled
This takes five minutes but saves hours of guessing. The error message tells you what really broke.
Quick Fixes That Actually Work
- Increase PHP max execution time to 120 seconds
- Increase WordPress memory limit to 256 MB or higher
- Exclude form pages from caching plugins
- Add AJAX URL to security plugin whitelist
- Disable nonce verification in Forminator settings (temporary test only)
Most Forminator problems go away after adjusting server limits or cache exclusions.
People Also Ask About Forminator Errors
Why does Forminator work sometimes but not always?
Because the failure depends on server load, form complexity, or time of day. Intermittent problems are usually timeout or memory issues.
Can caching plugins break Forminator?
Yes. Caching the form page can cache the security token. Once the token expires, submissions fail. Exclude form pages from cache.
Is Forminator less reliable than Gravity Forms or WPForms?
Not necessarily. Gravity Forms and WPForms face the same AJAX and timeout issues. The plugin is rarely the root cause.
Why File Uploads Break Forminator Most Often
File uploads increase form complexity significantly. Large files take more time to process. Server upload limits may be smaller than the file size. The AJAX request may time out during upload.
If your form has file uploads, check these first: PHP upload max filesize, post max size, and max execution time. Forminator shows a different error for file size issues, but timeouts often show as “Something went wrong.”
Related Form Plugins With Similar Issues
If Forminator continues to fail, consider Formidable Forms or Everest Forms. But expect similar AJAX challenges. The problem is usually server configuration, not the form builder.
Fluent Forms handles AJAX differently and sometimes works better on restrictive hosting. But test first before switching.
Final Thoughts
If Forminator shows “Something went wrong,” do not reinstall the plugin. Check your server limits first. Check your cache exclusions second. Check security plugins third.
In most cases, increasing PHP execution time to 120 seconds and excluding form pages from cache fixes the problem completely. The form was never broken. The server just needed more room to work.