If adding fields ‘counts’ as changing the structure, then yes we have for some, but not for others. It’s happening across multiple tables (but I believe they’re all in the same base). Again, it’s happening on so many different automations that we haven’t been able to systematically track it
OK, I will give this a shot, and thanks for the detailed answer!
One thing worth noting (and I may not have mentioned before): this is happening sporadically, and it will be a small-to-medium “burst” of several scenarios throwing the error at the same time.
Then they all run properly again. So I think it will be harder to catch the error, but I’ll give it a shot.
(and as a final clarification: we’re seeing 502 or 503 timeout errors from our AT modules occasionally, but the error code is distinct from these)
We’ve had 3 instances where this happens across several different scenarios:
Nov 28th: 8 unique scenarios, 1 on each
Dec 1st: 8 unique (they are not the same as Nov 28th), 1 on each, 7 instances from 1 scenario
Dec 2nd: 13 unique scenarios (some same as previou days), multiple instances from 5 scenarios
So at this point, we haven’t seen the error come up since Dec 2nd, and more importantly it seems like this is a corner-case issue, that hasn’t been seen widely by other users.
I think those are both good things?
Wanted to circle back with an update from Make Support:
As I have further checked the logs with this same error, it seems that the issue is within the Airtable server as it throws error 503. I would suggest reaching out to their support team if the issue still persists
We have not seen the issue again, but if it’s tied to 503 errors, I think it means we need to cut down our Watch Records triggers.
Thanks again to @loic.wiseflow for your insights, and hope this is helpful to others if you encounter the same issue.