Hi guys just FYI I've had this happen 3-4 times ov...
# questions
o
Hi guys just FYI I've had this happen 3-4 times over the last week (Astra). where it disconnects all my bases. Can you guys have a look into it, its quite frustrating
r
Hey @orange-computer-53672 – that definitely shouldn't be happening!
👍 1
@rich-pager-92385 will take a look
👍 1
r
Hey @orange-computer-53672, thanks for reporting this issue and my apologies for the inconvenience it's causing. I've been investigating this issue for a while now and have not yet found the root cause. So far I suspect if a sync run is taking way too long, the Airtable token we have can expire during the sync and for some reason the logic we have for automatically refreshing this is not working in this context. I suspect the connection is not disconnected, it happens that we were not able to finish the sync. We'll continue digging into the issue on our side Something I wanted to clarify with you is this issue happened at all before last week? Has anything with your setup changed by any chance? (e.g. more bases/tables being imported?)
o
Hi mate , yep definitely have been adding tables and or fields so assuming it’s to do with that
I’m currently modifying about 8 different bases so definitely assume it’s linked to all the changes
r
Thank you, that explains why the sync regularly keeps taking over 20 mins, but it should not randomly fail sometimes. (I've found several instances where the sync is longer than 30 seconds and the token refresh worked) One other explanation is that something outside of stacker is happening with your Airtable API usages which results in Airtable revoking the stacker assigned access token early. In the past we've observed Airtable being very eager in revoking access tokens, usually this would be due to some issue that happened between Stacker and Airtable, but we've not yet found any evidence of this. Please let me know if this rings a bell and there's a chance for the token to be getting revoked unexpectedly by Airtable
Hello Simon, just to update you on this, we've identified the cause and we think it's a rare "concurrency" issue that happens to occur often for you due to the volume of realtime updates being processed at the same time as sync. In summary, Airtable is strict about allowing only 1 refresh flow at a time via a refresh flow. In our case we'd have many workers processing changes for you and it can happen that two/more try to refresh at the same time, causing one to fail. We've started working on a fix for this and it should be available early next week Thanks for your patience with us on this issue!
o
Brilliant thanks so much for looking into it
r
Hello Simon! We've released a fixed for this issue yesterday evening (UK time) - We're keeping an eye on the release, but please let me know if you hit this issue again. Thanks again for reporting the issue and patience with it!
✅ 1
o
Hi @rich-pager-92385! FYI this is happening again today
I added a new field in airtable, and getting "inaccessable" on the data source table
I've forced resync about 5 times and it keeps making me re-authorise
this is what it looks like on the airtable side
Screenshot 2025-06-04 at 1.35.05 PM.png
r
Hello Simon, I'm looking into this now and looks like it's an authorisation config issue and different from the previous technical issue we saw. When your connection is trying to sync the base with id
appPupQyp541KBpnt
, it gets an error. I'm guessing you're not giving access to that base to get synced, or was your access removed from that base?
o
Hi mate, no adjustments to anything
I just added a new field to one of the bases
Screenshot 2025-06-04 at 5.40.11 PM.png
r
thanks for confirming. Can you please check that you still have access to whichever base
appPupQyp541KBpnt
points to? The error we're getting is a clear and specific one that we get once there's no access to a given base. Please let me know if it's not possible to check this easily on your side and I can look into getting some additional info via the Airtable API for your connection
o
interesting! I think that would be a base I deleted last week
how do we fix it from here?
r
Great, that explains the issue. We have a few options, easiest one is deleting the connection to this base from any of your apps which are using it. That would automatically remove this base from being synced and the issue will be resolved. Please let me know if this is not possible for some reason and we can make manual changes from our side to fix this
o
perfect, go for it
let me when when we can start refreshing !
r
I've removed that app for you now and have triggered a sync, I'll keep an eye on it to make sure it passes
o
cheers mate, seems to be kicking along now