Why Is My Google Form Not Accepting Responses? | Fix The Block

You open your form link, and instead of a clean submit flow, you see “The form is no longer accepting responses,” a sign-in wall, or a submit button that just won’t work. Annoying, right?

This page walks you through the real reasons Google Forms stop taking entries, plus the exact clicks to get your form open again. You’ll see checks for owners, editors, and people trying to respond. No fluff. Just fixes.

Start With These Two Checks Before Anything Else

Most “not accepting responses” cases come from one of two spots. Start here so you don’t waste time hunting ghosts.

Check 1: Is Response Collection Turned Off Or Closed?

Open the form in edit mode. Look for the control that stops new entries. In many forms, you’ll find it under the Responses area. In newer layouts, you may see response controls under the Publish flow.

If you see any wording like “Not accepting responses” or a closed status, flip it back on and test with a fresh browser window.

Check 2: Is The Form Published And Shared The Way You Think It Is?

Forms can look “ready” in edit mode while respondents still can’t reach a live version. If your form was created under the newer publishing flow, make sure it’s published, then confirm sharing settings match your audience (public, domain-only, or specific people).

After you change anything, open the live form link in a private window and try one test submission. That one step catches a ton of issues fast.

Why Is My Google Form Not Accepting Responses? Common Causes

When a form blocks entries, it’s almost always doing exactly what it was told to do. The trick is finding which setting is doing the blocking.

Response Collection Was Turned Off Manually

This is the classic. Someone toggled response collection off after the form hit its target, after a deadline, or by accident. People clicking the link will get a closed message (or your custom closed message, if you set one).

Fix: Turn response collection back on, then confirm the “closed message” isn’t misleading. If the message says entries are closed, responders may walk away even after you reopen it.

A Close Date Or Response Count Rule Kicked In

Google Forms has been rolling out better ways to stop entries by date/time or response count, so a form can close on its own when it hits a limit. That’s handy for registrations and quizzes, until you forget it’s enabled.

Fix: Look for any close scheduling or response limit settings tied to publishing or response settings. If you raised a response cap, set it higher than your current response count, or the form will stay closed.

“Limit To 1 Response” Is Blocking Repeat Submitters

Sometimes the form is open, yet one person insists it won’t accept their entry. If “limit to 1 response” is enabled, anyone who already submitted from that account can’t submit again.

Fix: Decide what you want. If multiple submissions are allowed, turn that limit off. If you want single-entry behavior, keep it on and tell respondents they must switch accounts or ask you to clear their prior entry (if your process allows it).

Sign-In Or Domain Restrictions Are Too Tight

Forms can require a Google sign-in. They can also be restricted to people in a specific Google Workspace domain. That’s great for internal surveys, but it blocks personal Gmail accounts and guests.

Fix: If you expect outside responses, loosen the restriction so anyone with the link can respond, or set access to the right audience before you share the link again.

The Link Is Right, But The Person Is Opening It Wrong

On phones, a form link opened inside an in-app browser (social apps, chat apps) can behave oddly. A sign-in step might loop. A submit click might not complete.

Fix: Ask the respondent to open the link in their full browser (Chrome, Safari, Firefox), or copy the link and paste it into the browser address bar. This often clears the issue in one move.

A Section Rule Or Validation Rule Traps The Respondent

Owners sometimes think “not accepting responses” means the form is closed, when it’s actually a logic trap. Common ones:

• A required question hidden behind section logic.
• A response validation rule that rejects normal input (date format, number range, text pattern).
• A choice that routes to a dead end where the submit button never appears.

Fix: Use Preview mode and try to complete the form like a stranger would. Pick edge-case answers. Try a phone. Try a desktop. If you can’t reach Submit with normal behavior, revise the rule or the routing.

Someone Copied Or Moved The Form And Changed Ownership

If a form was copied into a shared drive, moved between accounts, or handed off to a new owner, access settings can shift. Editors may assume it’s public when it’s locked to a domain or a small sharing list.

Fix: Re-check sharing settings from the current owner account. Then test the live link as a non-owner.

The Form Is Open, But Responses Aren’t Being Recorded Where You Expect

This one feels like “not accepting responses” even when the form is working. The responses are landing in the form’s Responses tab, yet your linked spreadsheet isn’t updating, or you’re looking at the wrong spreadsheet.

Fix: Verify which spreadsheet is linked, confirm you’re in the right Google account, and check the form’s Responses tab first. That’s the source of truth.

Browser Extensions Or Privacy Settings Block Submission

Ad blockers, script blockers, hardened privacy settings, and some corporate security tools can break form submission. It may show up as a submit button that spins, then fails.

Fix: Test in a private window with extensions disabled. If it works there, you’ve found the cause. For respondents, the clean fix is switching browsers or disabling the blocker for that one page.

Google-Side Outage Or Workspace Policy Changes

It’s rare, yet real. A service disruption or an admin policy in Google Workspace can block forms, limit sharing, or restrict external sharing.

Fix: Try the form from a personal device and network. If it works outside your org network, ask your Workspace admin to check sharing policies. If it fails everywhere, wait a bit and re-test; outages usually resolve without any form edits.

What You See	Where To Check	What To Do
“No longer accepting responses” message	Responses / Publish response controls	Turn response collection on and retest in a private window
Form loads, Submit never appears	Section routing and required questions	Fix branching so every path ends with a Submit screen
Person says “I can’t submit,” others can	Limit to 1 response and sign-in rules	Turn off one-response limit or have them use the allowed account
Sign-in prompt blocks guests	Sharing and respondent access settings	Allow anyone with the link, or share to the right accounts
“You need permission” or domain-only access	Workspace domain restriction	Allow external responses or collect only from your domain
Submit spins, then fails	Extensions, trackers, corporate security tools	Try private window, switch browser, disable blockers for the page
Responses “missing” from spreadsheet	Form Responses tab and linked sheet	Confirm the linked file, then re-link if you connected the wrong sheet
Form was copied or moved to a new account	Ownership and sharing settings	Re-check access settings from the current owner, then test live link
Close date or response cap hit	Close rules and response limits	Raise the cap or remove the close rule, then publish changes
Only fails inside an app (Instagram, Slack, etc.)	In-app browser behavior	Open in full browser or paste link into Chrome/Safari

Fixes For Form Owners: Click-By-Click Checks That Work

Once you know the category of the issue, fixes are usually quick. Run these checks in order. Each one has a clear pass/fail result.

Reopen Response Collection And Set A Clear Closed Message

Open the form in edit mode. Go to the response controls and confirm the form is accepting entries. If your interface shows response settings tied to publishing, check there too.

If you previously used a custom “closed” message, replace it with something neutral once you reopen the form. A stale message can confuse users even when the form is open.

Google’s own help page on managing responses includes the response stop controls and related response settings. View & manage form responses

Confirm Share Access Matches Your Audience

Ask one blunt question: who should be able to respond?

• If the answer is “anyone,” remove domain-only restrictions and avoid sign-in requirements.
• If the answer is “our company,” lock it to your Workspace domain and keep sign-in required.
• If the answer is “a short guest list,” share to those accounts and test with one of them before you send the link widely.

Then test as that person. Open an incognito window and try the link. If you can’t reach the form without being signed into your owner account, your audience won’t either.

Check Close Rules Tied To Date Or Response Count

If your form is meant for registration or limited slots, a close rule may be the reason it shut. Google has been adding easier ways to close by time or count, which is great when it’s intentional and confusing when it’s not.

If you want entries to keep coming, remove the close rule or raise the response cap beyond your current total. If you want it closed, keep the rule and set your closed message to point people to the next step (email, next event, new form).

Google’s Workspace Updates announcement describes the rollout of closing by date/time or response count for Forms. Set Google Forms to automatically stop accepting responses based on date and time or response count

Audit “Limit To 1 Response” And Collect Email Settings

Single-response settings are easy to forget after you test the form yourself. If you filled it once during setup, you might block your own second test.

Decide what fits your use:

• Event registration: one response per person often fits.
• Bug reports: multiple responses can make sense.
• Class quizzes: one response per student is common, paired with sign-in.

After you choose, test with two different accounts. That tells you instantly whether the setting is behaving the way you expect.

Test Branching And Validation Like A Stranger Would

Form logic issues hide in plain sight. The form owner knows the “right” path and never hits the trap.

Use this simple method:

1. Open Preview mode.
2. Try one run where you answer quickly, like a rushed respondent.
3. Try one run where you choose edge answers (the last option in a list, “Other,” blank-looking options).
4. Try one run on a phone.

If any run ends without a Submit button, your routing needs a fix. Make sure every section path leads to a final submit screen.

Fixes For Respondents: What To Try When You Can’t Submit

If you’re the person filling the form and it won’t take your entry, you can usually get unstuck with a few practical moves.

Switch Accounts Or Use The Right Sign-In

If the form is restricted to a specific domain or requires a Google sign-in, your account matters. If you’re signed into the wrong Google account, you can hit a silent block.

Try opening the link in an incognito window, then sign in with the account you were asked to use. If the form is meant for a school or workplace, your personal Gmail may not work.

Open The Link In A Full Browser, Not Inside An App

In-app browsers can break sign-in flows. Copy the form link and open it in Chrome, Safari, or Firefox. If the page suddenly works, the issue was the in-app browser layer.

Check For Red Error Text And Validation Rules

If you can click Submit but it won’t go through, scan the page for red text and required fields. A hidden validation rule can reject your input even when it “looks fine.”

Try these quick tweaks:

• Re-enter number fields without spaces or commas.
• Use the date picker instead of typing the date.
• Shorten long text in a single field and try again.

Try A Clean Session

Open a private window or switch browsers. If it works there, your normal browser likely has an extension or setting that blocks submission scripts.

Scenario	Best First Move	Next Move If Still Stuck
Closed message shows up	Ask owner to confirm response collection is on	Request a fresh link after they re-publish
Sign-in wall appears	Sign in with the requested account	Use an incognito window to avoid account mix-ups
Submit button fails or spins	Switch browser or use private window	Disable blockers for that page and retry
Submit button never appears	Scroll to the end and check section navigation	Tell owner which answer path you chose so they can fix routing
“You already responded” type block	Use a different allowed account	Ask owner if one-response limit is enabled
Works on desktop, fails on phone	Open link in mobile browser app	Try a different phone browser

Why Is My Google Form Not Accepting Responses? Fast Checks Before You Share Again

Once you think it’s fixed, do a short re-test so the same issue doesn’t pop up five minutes after you post the link.

Run A Two-Minute Owner Test

1. Open the live link in an incognito window.
2. Submit one test response.
3. Confirm the response appears in the form’s Responses tab.
4. If you use a spreadsheet, confirm the same response appears there too.

Run A Two-Minute Guest Test

Ask one person who is not an editor to submit a test entry. Pick someone who matches your real audience (guest, student, coworker in your domain). If they can submit cleanly, you’re ready to share.

Lock Your Final Settings So You Don’t Re-Break It Later

Most breakages happen after the form goes live. Someone tweaks a setting, sets a response cap, or tightens sharing to stop spam, then forgets to loosen it later.

If you need control, write down your intended settings in one place:

• Who can respond
• Whether sign-in is required
• Whether one response per person is enforced
• Whether the form closes by time or count
• What message shows when the form is closed

That tiny checklist saves you from reopening this problem the next time you recycle the form for another event.