Google Forms Error: "No Longer Accepting Responses," but Form Should Still Be Collecting Responses


U-M Google, Google Forms


The Google Form I own says that it is no longer accepting responses, but I need it to keep collecting them. Why is this happening? How do I fix this so the form can continue to accept responses?


If you are the owner of a Google Form that is showing the error that it is no longer accepting responses, there are a few possible reasons why:

  • A collaborator with Editor access to the Form has turned off responses without your knowledge
  • You are accepting file uploads with the Form, and...
    • You or a collaborator moved the Form into a Google shared drive
    • Your U-M Google account is near/over the assigned storage limit
    • The parent/top-level shared folder where the Form resides is owned by a U-M Google account that is near/over their assigned storage limit

To fix these issues and allow your Google Form to continue to accept responses, refer to the sections below.

Collaborator has turned off responses

You should consult with the Editors assigned to the Form before turning responses back on. To turn responses on:

  1. Open your Google Form
  2. Click the Responses tab at the top
  3. Toggle the "Accepting responses" switch to ON

Form with file uploads

Form was moved into a shared drive

The file uploads option is not available if the Form is stored in a Google shared drive. If an existing Form with file uploads turned on is moved into a shared drive, the Form will automatically stop accepting responses, and you will not be able to turn them back on until you either remove the file uploads option or move the Form out of the shared drive.

Your account is near/over the storage limit


  • The Form is owned by you
  • Does not reside in a shared folder owned by someone else
  • You are near or over your storage limit
  • The file upload maximum size is set to an amount that would cause your account to go over the storage limit,

Google automatically stops accepting responses if the account that owns the file upload Form responses is near or over their storage limit. You will either need to reduce the amount of storage in your account or transfer ownership of the Form and the responses to someone who is not near or over their storage limit in Google.

The Form resides in a shared folder owned by an account near/over the storage limit

Occasionally, Google will prevent collaborators from adding or editing files in affected folder structures where the parent/top-level shared folder is owned by someone whose storage is full. This can sometimes include any files you own that reside within that folder structure. Therefore, if you own a Google Form that resides within a shared folder owned by someone else, it is affected by the folder owner's storage limits.

Forms with the file upload option turned on automatically collect file uploads in a folder. Since your Form is within the folder structure of someone else, the file uploads folder is also within that structure. If the top-level shared folder owner is near their storage limit and the maximum file upload size is set large enough that a file uploaded of that size would cause the shared folder owner to go over their storage limit, Google will automatically stop accepting responses to the Form.

You will either need to ask the shared folder owner to reduce the amount of storage in their account or move the Form and its responses out of the affected folder structure.

Additional Information

Need additional information or assistance? Contact the ITS Service Center.

Print Article


Article ID: 9577
Mon 1/23/23 2:17 PM
Mon 1/22/24 3:20 PM

Related Articles (3)

This article includes information on why the "File upload" option is unavailable for Google Forms stored in Google shared drives.
This article explains how to share Google Form responses and attachments in Google Drive.
This article provides information on what happens when someone reaches their storage limit/their storage is full in their U-M Google account. It also states what you should do if this happens.