Elementor form not submitting: silent send

A successful send and a failed send can look identical to the visitor. In both cases the button returns to normal, and the fields may or may not clear. If the success message sits above the visible part of a long page, or in a section the page hides after submit, the visitor concludes nothing happened. They press again, and the second press lands in your list. The owner then sees two entries from one person and suspects the sending, when the real fault is the missing message. A visitor who saw nothing rarely writes back to say so.

• Press Submit with valid values and take a screenshot of the full page, not just the visible part, to find where the message appears.
• Check whether the fields clear after a successful send, since a cleared form is the only sign some visitors get.
• Open the browser console on the press and note any failed request or refused response from your site's server.
• After each press, look for a new entry in your submissions list and count it against the presses.
• If the form redirects after submit, confirm that the target page exists and loads on a phone.

The success message can sit inside the form area, or the owner can move it, restyle it, or send the visitor to another page instead. A message placed far from the button can sit below the fold on a phone, and a visitor who has not scrolled sees the button return to normal and nothing more. A redirect works only when the target page exists and loads, so a broken thank-you page turns a good send into a dead end. Check the screen after the press at full width and at phone width, and note which element holds the message, because the visitor has to see it where they were looking.

A request can also fail with no visible sign. The form posts to your site, and a caching plugin can serve a copy of the page that carries an old security token, which the server then refuses. A rule in a firewall or a security plugin can do the same. The visitor sees the button return to normal with no message, because the error line is either styled out of view or never filled in. The entry never arrives, so the owner sees nothing either. The browser console on the press is where this shows up, as a refused request with a status that is not a success.

Each run presses Submit with valid values and records what happened on screen. The report gives you a screenshot of the full page after the press, the element that held any message, the state of the fields, and any failed request logged at that moment. The run cannot read your submissions list, so it cannot confirm that an entry was saved. Count the entries yourself after a run and match the number to the presses it recorded. A shortfall points to a failed send, and a full count with no message on screen points to a placement problem.

Caching rules, security plugins and theme updates change how a form page is served, and a change can hide the message or refuse the send with no edit to the form itself. Rerun the same simulated visitors after each change, on a laptop and a phone, and check that each one sees the message and that the entry count matches the presses. A visitor who presses twice creates a duplicate entry, so the count matters as much as the screenshot.