Hi <@U03QRSSRX6U>, I have tried syncing the data i...
# questions
o
Hi @rich-pager-92385, I have tried syncing the data in this test database all weekend, and it still isn't bringing the records across. You can see in screenhost "updated 28 mins ago" but never comes in. can you take a look when free?
r
Hey Simon, can you please share the airtable base id please? (Any additional info would also be useful in debugging, e.g. the Stacker URL for this app, the stacker app name, etc)
r
From our logs I've found that the 4 records are imported from Airtable (and have ids:
receAKe2D9Y58rN75
,
recOANorUCzggZWm6
,
recy1xdSHbPlLVcM
,
recGCLFeOEw61YmTK
) but they've not propagated through our system components fully to be shown in your app. This can happen if the apps, or data sources went through an unexpected sequence of events and didn't give enough chance for the data to propagate fully. Can you please help me with the following question to get the to the root cause faster? 1. Was there any issues/glitches during the process for adding the base? 2. Was this base added and removed quickly, and then added again? 3. Is this base imported into any other apps/workspaces? Any additional context you can share will be helpful in finding the root cause
I've found one of the main symptoms of the issue and fixed it. I think you should now be able to see the records for this object, please let me know if not. I'm going to check the other objects in your app and fix those if needed too
(I'll write a summary of the findings soon)
o
Cheers!! Will test
r
Two of your other tables (airtable ids: tbl1LYot58nCIg2dE, tblRMDdrPnr8jLOZZ) were also impacted by this issue, I've fixed those too. We still don't know the root cause and the questions I asked would still be helpful in finding the root cause. It looks like there was some kind of other event happening during your imports that meant the process to import the data fully didn't complete. Regardless of the root cause, our system should be able to recover - I've raised this internally and we'll work on improving it, thank you for raising it and please let me know if any of your other tables are affected.
(I also have it on my list to look into your schema issue today - I'll quickly double check now if that's the same issue as this)