Your survey won't save
Updated 2026-09-02
Clicking create and having nothing happen almost always means one of three requirements is missing. The button checks them in this order, so whichever error message you see is the first one it found.
Check these in order
- No title. You will see "Please enter a survey title." Type something in the title field, even a short working title. It is shown to respondents, but you can keep it simple.
- No questions. You will see "Add at least one question." A survey needs at least one question before it can be created. Add a question and choose a type for it.
- The CAPTCHA has not been completed. You will see "Please complete the CAPTCHA." Scroll down to the CAPTCHA box near the create button and complete it. If it looks stuck rather than unfinished, see the separate article on the CAPTCHA not completing.
Nothing is sent to the server until all three are satisfied, so none of these will show up as a network error or a loading spinner that hangs. The page shows the message and stops, right where you are, with everything you already typed still in place.
Why the button seems to do nothing
These three checks run in your browser before your survey is sent anywhere, which is why there is no loading spinner, no delay, and no network activity when one of them stops you. The page is not thinking; it already knows what is missing and is telling you immediately. That also means none of the three can be a connection problem or a server issue on our end. Fixing the specific thing named in the message is the entire fix.
Still not saving after all three are fixed
If the title is filled in, at least one question is added, and the CAPTCHA shows as complete, but the button still does not seem to do anything, try reloading the page once. Occasionally a question added earlier in the session is left in an incomplete state, such as a multiple-choice question with no answer options typed in, which can behave like a missing question even though one is technically present. Reopen that question and confirm it has the pieces it needs.
If a save is attempted and rejected by the server rather than stopped before sending, you will see a different, more specific message rather than one of the three above. That points to a different problem than the one this article covers, most often a duplicate custom link if you set one, or too many attempts in a short window.