Additional Information: This is happening as there is a hidden linked field that is prepopulated in the URL. This doesn't get prepopulated if the user is not logged in, although if its unhidden they can choose from the list? 

I am having the exact same problem, except the person is signed in and I have a requirement on the form that the person is signed in to see the form.

I think the cause of the issue is that I had been updating some settings on the form when someone tried to submit to it, and now she can't use the form at all. She has tried:

• Refreshing the page
• Clearing her browser cache
• Restarting browser
• Clearing her form entries
• Signing out of Airtable and back in

Having the same issue, with two different users, one that was probably in the same situation as described by @Tina_Wheeler, but the other just tried to use the form after being set as final.

In contact with support, but so far no solution.

Got this info from support, which kind of works, but reduces functionality:

This may be occurring due to the user having read-only base permissions but attempting to submit a form, which in some cases will be treated as a record-create action (thereby preventing the user from submitting the form).

This can be overcome by enabling the form to be accessible by anyone with the link [...] while also turning off the toggle to track submitters

I tried restricting to our domain and keeping the toggle to track submitters on and it also worked.

Thanks for the clarification,l I assumed it was something like this but does really restrict the usage of it  

I'm having this same issue, but restricting to our domain is not an option for me. I really need to be able to give access to anyone on the web. Are there any other workarounds I could try?

 Hey people, Im having the same problem, I have people that are signed in and people that are not, and both cannot finish submiting the form. I need this solution not only restricted to our domain as well, any ideas?

I had this issue pop up for me this week for a form that was publicly available. An email support technician with Airtable told me it could be related to fields that are conditionally visible. Here's what she said: 

Another reason this error may occur is when fields used on the form are conditionally visible, but the conditional form field contains an invalid condition due to an underlying field change or deletion.

To confirm if this is happening, please navigate to the form in your interface editor, open the conditions for all of your conditional fields, and look for an “invalid condition” error. Here's a quick GIF showing an example of what this may look like. If you find one of these, you will need to fix or delete the condition and then publish the form. Please note that this may be happening on multiple fields, so you'll want to check all conditional fields. 

Sure enough, that was my problem. A quick fix and my form was back to working again. Hope this helps. 

I am having the same issue -- it is occurring when I have had to make changes to the form after sharing the link with people.  (It is a form that is open to all.)  When people are trying to submit their answers, they are getting error that the form has been changed and it to refresh the page, but it loops them through the same error.  We have nothing setup as conditionally visible.   Is the issue that once the link has been created or shared, that no further changes can be made to the form?   If so, that really cuts down on the real world use of the form.

Hi! I am having this issue too. My form is limited to people who have access to the base. I use my form for time collection for contractors. I don’t really want to make them “Creators” with full access, but I’m feeling that needs to be the fix. The parameters for my form:

• Accessible to anyone with access to the base
• I have an “assignee” field that defaults to the logged in user.
• The “Projects” field allows the user to select any project  where they are the assignee
• Also have a condition that allows certain users to input date & hours worked vs in/out HH:MM:SS time entry, again, based on assignee/logged in user.

My user IS using their correct email to access.

They have “commenter” access to the base & interface

I don’t see any errors with my conditions.

Worst part… It works FOR ME, so I don’t know how to triage this for the user since I can’t log in as him (I want this feature BTW Airtable!!!)

Also, is anyone finding the new form view has “zombie” forms? I only have 1, live form and I’ve repeatedly deleted some of the other test & unpublished forms I’ve made. THEY KEEP SHOWING UP in the Form builder view. HALP...

Hmm, a couple things potentially going on here…

Before I get to those, obligatory statement here, go try using Fillout forms for this purpose instead, it will probably solve the workflow and permissions issues you’re trying to circumvent. 

Not quite sure what the issue could be, but have you tried various troubleshooting steps such as…

• Temporarily upping this user to editor and seeing if that impacts the situation?
• Building your form as an interface or top level form instead of a view?
• Spinning up another free Airtable account with a different email address to see if the issue is replicated? 

I would prefer not to use Fillout if I don’t have to. I already have a form builder in my stack and hate to have to add another one.

have you tried various troubleshooting steps such as…

• Temporarily upping this user to editor and seeing if that impacts the situation?
• Building your form as an interface or top level form instead of a view?
• Spinning up another free Airtable account with a different email address to see if the issue is replicated?

I’m making him an editor, so we will see if this fixes it.

I have an interface and have embedded the form there-- are you suggesting re-building the form in the interface instead? 

Great idea on the free account. I’m going to try that.

THANK YOU for your response!

Haha, there are so many ways to create forms in Airtable it’s hard to describe them right. Aside from the oldest method of a view in the data layer, there are also specific interface form pages as well as the top level forms. You can always try rebuilding in a different one (see my screenshot) 

If you’re using a form built originally as a view, those are quite old and maybe there’s some issue there. 

Also, if Airtable is the form builder in your stack, it’s not great for that purpose, it's much more of a database tool with some slightly janky forms slapped on. Fillout’s free tier works for most purposes and is lightyears ahead of AT for forms (hence the obligatory recommendation haha).  

I know that ​Jennifer doesn't want to add another form tool to her stack, but for everyone else in this thread, I have to strongly recommend what @DisraeliGears01 said above:

In my personal opinion, the best way to workaround this Airtable bug is to use Fillout’s advanced forms for Airtable.

With Fillout, you can create a login page for your form, which will give you these options:

1. Fillout will allow you to restrict the user’s login based on a pre-approved list of email addresses that you have stored in Airtable. (You can also restrict the logins by SSO or email domain.)
2. You can verify & confirm that the user is typing in a valid email address.
3. You can limit form entries to one entry per person.

Hope this helps! If you’d like to hire an expert Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Thank you for clarifying this. I will check it out. 

I’ve been using Jotform for years, before I started using Airtable and I love it, so I’m hesitant to move everything over to fillout at this point since I have a nice deal on a paid account with them.

LOL on the “janky forms” yea, I agree. This form was originally a view form, but when the new form builder came out, I completely rebuilt it using that instead. BUT that’s when the problems started.  I liked how it was able to filter projects according to who was logged in. I will play with re-creating the form again IN the interface. I was just thinking there probably isn’t a big difference and it would be the 4th time I’ve rebuilt...Le Sigh…

Do you know offhand if Fillout can replicate my form conditions that I listed above? It’s important to me that the “Assignee” can be the “Current user” and that I can filter projects based on if they are assigned or not…

Again, thanks so much for your speedy response. I really appreciate your time & engagement and this community. 

Hi ​@Jennifer_Ching,

You’re welcome!

Yes, absolutely, you will be able to replicate all of the same functionality that you currently get in Airtable’s forms with Fillout’s forms, and so much more!

And Fillout is superior to JotForm because it was designed from the ground up to communicate directly with Airtable.

In your case, you will probably want to create a login page, which will let Fillout know what the user’s email address is. However, you could also have the user just type in their email address into a field — or just select their email address from a dropdown menu. It just depends on how much security you want on your form.

Then, you would use Fillout’s advanced filtering features to filter your linked record field to only show the user the projects that are assigned to their email address.

For you, the only problem that you’re going to face is that Fillout can’t currently read “User” fields from Airtable, so you’ll need to figure out a way to have an email field or a lookup field in Airtable that displays the User’s email address for each project.

Outside of this, you’re going to love all the other Airtable-specific features that Fillout offers, such as the ability to:

• Update existing Airtable records using a form
• Display Airtable lookup fields & Airtable attachment fields on forms
• Create new linked records on a form
• Create PDF documents from form submissions, and then attach those PDF files to the Airtable record

I show how to use a few of the advanced features of Fillout on these 2 Airtable podcast episodes:

• Using Fillout to create an eSignature approval process with PDF file creation.
• Using Fillout to create an order entry form with line items.

Hope this helps! If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

​@Jennifer_Ching Ah, I had this exact issue!  For me I had an Interface form that was set to ‘Only users with base access’, and users with ‘Commenter’ access would hit that ‘Refresh page’ error. 

The fix for me was to make it accessible to anyone on the web, and once I did that the error went away

​@TheTimeSavingCo Brilliant. I just modified my form and SNAP it works!

​@ScottWorld I am gravitating toward Fillout as a solution...It doesn’t natively integrate with LeadConnector or HighLevel, so I think I’m gonna have to use zapier, which sucks, but is still doable. In your experience is Fillout the kind of company who is working towards & prioritizes integrations like that? JotForm still is king in that area.

Thank you BOTH so much. I love this community!

Hi ​@Jennifer_Ching,

I would never ever ever recommend Zapier to anyone.

If you’re looking for integrations, I would only recommend Make’s advanced integrations and automations.

Make is INFINITELY more customizable and powerful than Zapier, yet it is significantly cheaper too.

I wrote an entire post here comparing Make vs. Zapier.

Since you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable.

I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.

I can definitely help you with all of this, too. If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Ha nice glad I could help

For the Fillout integrations stuff, you may want to just open a support ticket and ask them directly about it; my experience with their support people has been pretty decent.  At the very least they’ll probably add your request to the backlog which might help move the needle