Maybe somebody is facing something similar starting today? When trying to submit a form the following error appears (below). There were no changes to the Base. Also, the same started to happen to an older (4-5 months old) version of the same base. To add more, one of our automations started to act up - We have an automation which fills in 2 "single-select" fields, where the second field is a limited view depending on the first field. This error comes in "invalid item in array cell: foreign record is invalid: row is not visible in column view restriction". Both of these issues appeared out of nowhere. We do have only 1 GB and 10,000 records left in the plan (also tried to making some more to see if that help - it doesn't), but it doesn't seem like it can be an issue.
"Cannot process form submission
Oh no! Somebody made changes to the structure of this form after you loaded it. You'll need to refresh this page to submit your form responses, but when you refresh the page, the information you’ve already entered here will be not be saved.
If you’d like to save anything you've written, please copy and paste your text responses somewhere else (like a word processor) before refreshing the page."
Also experiencing similar issue starting yesterday (Feb 1). An automated script that has been working flawlessly for months now returns
"Error: invalid item in array cell: foreign record is invalid: row is not visible in column view restriction."
I have went through every single view and made the field of interest visible as a possible workaround, but have had no luck solving the problem. The form I tested worked fine though.
Interestingly, when the issue was first occurring it would throw a "Refresh this page" error whenever I tried to link to another record. That seems to have been solved but my script still fails for no valid reason.
Hello, we did identify where the issue started to surface. Our situation:
a) Single Select (just a list from another Table)
b) Single Select (with a filtered view). And that filtered view is changing depending on first Single Select. And then, when I’m adding a) and b) via a single automation, it adds value for a), but then the options for b) don’t get in time to be populated and the automation tries to push in the value, which gets rejected.
So in order to resolve business critical problem, we had to simplify our processes and get rid of filtered view for b), and it started to work (though with degrated processes now)
Thanks for your input! I was able to find the root of our problem. I had a restriction on linking to a record only in a specific view (that has never been an issue before) but removing this has allowed things to start working again. Nonetheless this is an Airtable issue, I believe. Must have to do with a slowdown in views refreshing or something.
Thanks for posting your solution, it really helped me!
Having this same issue on an automation workflow. I do have, "Limit record selection to a view" but I can't just turn it off. It's essential to my workflow that users can only pick from a selection but that the automation can assign a value that is not available in that selection. Hope this is a bug and not a sudden and intentional change on Airtable's part.
Yes we were lucky and our automation is always linking the records without user intervention, so I was able to turn this off. I expect it is a bug that will be solved. Interestingly, it was an issue for us for about 10 minutes at first and then returned to normal. Then a few hours later it started happening again and continued to be an issue until the next day when I made the change to the restrictions. The fact that it was intermittent at first makes me think it is a bug and not intentional.
Enterprise support just got back to me saying:
"We've had a couple reports of this issue and the team is currently investigating. You have already come across the workaround (removing the restriction) but we understand that this is ofcourse not ideal."
Thank you so much @Albert for sharing this work around, like our support team mentioned this is not ideal for the time being. If anyone is having this issues please also reach out to your support team.
We will be featuring this post to help those facing this issue.
My team is also experiencing major issues due to this bug. We cannot remove the restrictions due to the function of our base and we are getting nervous. Are you expecting that this will be solved at some point in the near future? Or will we have to find our own workaround?
Thank you all for your patience as our teams worked on a solution for these issues and we apologize for any inconvenience this may have had with your workflows!
Please refer to our Airtable Status page if you experience any incidents in the future.