Google form not submitting after section: rules

A multi-section form runs on jump rules. Each section ends with a page break, and the break can go to the next section, to a named section, or to Submit. Multiple choice and dropdown questions can route by answer, so one choice may jump ahead and another may jump back. Visitors who pick the answer the owner tested never reach the stop, and the owner's own run takes the same path every time. A file upload question adds another wall: it asks the person to sign in with Google first, and a visitor who cannot sign in is stuck on that page.

• List every page break and the rule it carries: next section, a named section, or Submit.
• Walk each answer on each routing question in preview, and note every path that ends without Submit.
• Find any rule that sends visitors back to an earlier section, and trace the loop it makes.
• Look for a file upload question, which asks for a Google sign-in before the page moves on.
• Check that every rule points at a section that still exists in the form.

Each section ends with a page break that carries a rule. The rule may send the visitor to the next section, to a section the form names, or to Submit. When a multiple choice or dropdown answer decides the route, each option carries its own target. An option set to a section above the current one sends the visitor back over answers they already gave, and nothing on the page says which option caused it.

The fault often sits in the section before the stop, not in the one the visitor is on. The page break you see controls where the visitor goes after the current page, so a stop on section three can come from an answer picked on section two. Read the rule on every page break in order, from the first section to the last, before you test a single path.

A file upload question needs the person to sign in with a Google account before the file can be added. A visitor who is signed out, or who is in a browser that blocks Google sign-in, cannot pass that page. The form looks stuck on a section, and the visitor has no reason to think a sign-in is the cause.

The fix is to remove the upload, or to move it to the end of the form and say a sign-in is needed before the section starts. A form with an upload question cannot be filled in by a signed-out visitor, and a simulated run cannot sign in with Google to get past it. Decide which of those you want before you change the rule.

Give the visitor the answers that cause the stop, such as a parent who picks the beginner swim level, and start it on the camp's sign-up link. The run follows those answers and reports each section it reached, the button it pressed and the text on the screen, with a screenshot. If Next sends the visitor back to a section, the report shows that section again, after the answer the visitor picked.

A run covers the paths its visitors take. It does not walk every route through the form, so one clean run does not clear the form. Run visitors with different first answers, then walk the rest by hand in preview. The run does not read the rules, so it cannot tell you which page break is set wrong. Write down each path you walked, so the next change is checked against the same list.

Adding a section, renaming an option or deleting a page can leave a jump rule pointing at the wrong place, and the stop returns for the next visitor who picks that answer. Rerun a visitor for each option after each change, and walk every path in preview. Owners who share the form through a link on a phone repeat the run on a phone as well.