Save the date! Join us on October 16 for our Product Ops launch event. Register here.
Feb 02, 2023 12:51 AM
Greetings,
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."
Feb 02, 2023 08:54 AM
Sounds like good news. Thanks for the update!
Feb 02, 2023 10:30 AM - edited Feb 02, 2023 10:31 AM
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.
Feb 02, 2023 12:23 PM
Hi Chris,
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?
Feb 02, 2023 05:00 PM
It seems that this is now resolved on my bases!
Feb 02, 2023 05:46 PM - edited Feb 02, 2023 05:46 PM
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.
Feb 03, 2023 06:45 AM
Confirmed fixed on my workflows. Thanks!