HubSpot form not submitting: rejected input

The embed draws every field on the page, which makes the owner believe the form is working. It only means the fields loaded. A consent checkbox added under the last question can be required, and a visitor who skips it gets an error at the bottom of a long form. An email address on a domain the owner has blocked can be refused with no message on the field at all. A visitor who has filled the form before may see different questions, which the owner never sees while editing. Each of these looks like a button that does nothing.

• Submit an empty copy and note every field and checkbox that shows a message, including those below the button.
• Check which boxes are required in the form editor, especially consent boxes added for a privacy notice.
• If the form blocks any email domains, enter an address on one and see whether the form says why it refused.
• Submit once in a private window, then open the page again in the same window to see whether the questions changed.
• After each test, check the form's submissions list to confirm the entry arrived with the values you expect.

The form checks each field, and it checks the consent box too. A privacy checkbox added near the end can be required, and an owner who never tests a submit that skips it will not see it fail. The visitor reads the questions, reaches the bottom, presses Submit, and finds a message beside a box they did not register as a question. Email fields refuse a value that fails the format check, and a blocked domain can refuse an address that looks fine to the visitor. Find each required field in the editor, then compare that list with what a visitor sees on screen, because the two can differ.

Some HubSpot forms ask someone who has already filled them in different questions. The purpose is to ask new things over time instead of repeating the same ones. It does mean the form a returning visitor sees can hold fields a first-time visitor never saw, and the owner, editing it, sees only the full list. A stranger who submits twice in one browser can meet a second version they did not expect. To check it, submit once, then open the same page in the same window and read the fields again before you test a second time.

Each run fills the form in order, presses Submit, and records what came back. The report gives you the field or checkbox that carried a message, a screenshot of the screen after the press, and any failed request or script error recorded at that moment. If the press changes nothing and no message appears, the run says so, which is the case where the service refused without a word. The run does not read your submissions list, so check that list yourself after the run to confirm whether the entry arrived.

Adding a consent box, making a field required, or changing the domain rules can turn a working form into one that refuses every attempt that skips it. Rerun the same simulated visitors after every edit, including one that skips the new checkbox, and confirm the confirmation appears. A visitor who gives up leaves no entry in the submissions list, so a rerun is the quickest way to see the attempt that failed.