Is there a known AirTable sync issue today? I have...
# questions
p
Is there a known AirTable sync issue today? I have been stuck on a sync for 30+ minutes this morning. I have tried restarting the sync, reauthenticating my connection, and logging out of Stacker so far without success - I am getting hung up on this step:
👀 1
s
Hey Nick, is your data still syncing or are you able to completely sync your data now?
p
Hi @silly-pharmacist-44942 - no, I am still stuck on the same step in the sync. The issue started this morning when I noticed a number of fields had de-synced, specifically all of the image fields. I tried to run a sync and have been stuck on the step above ever since.
I have experimented with adding new records in AirTable - I am seeing them on the data grid, but just in their initial state, no changes to the data on the AT side are syncing
👀 1
r
Hey @prehistoric-dusk-53109, I've been looking into this. It looks like your schema sync is in a bad state and that's also causing your data sync to be stuck in a bad state. One of your records with id
receLWzvnrB5QWGW9
is duplicate in a column somewhere where the schema sync is trying to add a "uniqueness constraint" Did you by any chance change a multi-link to be a single-link? Or perhaps changed the primary field of an object?
I believe the name of the field with duplicate values is
user_requests
on your side. Can you please confirm if this column has duplicate values within your base?
p
hello @rich-pager-92385 I just saw your note here - checking now
looks like this might be the issue - that field was changed to be a single linking field. I changed it back to multi and the sync went through just now
I'm also seeing the data I was missing in the data grid and on my layouts now too.
Thanks for your help @rich-pager-92385
r
Excellent, thank you for confirming the issue Nick and glad I could help! My apologies for the root cause of the issue, in Astra we have a different architecture to handle link fields and looks like we're much more strict in Astra hence this issue. We'll continue looking into the root cause and hopefully fix it soon
🙌 1