With the recent introduction of the limit of 100 synced downstream bases per upstream base, we realise that one of our bases has over 200 such downstream synced bases, exceeding the limit. So we receive the error "The source application has reached t...
I noticed three records missing from a table, which had been created via an API call. The API call response indicated success, including a response object containing the same number of records (and with recIDs) as had been POSTed in the call. However...
How might one identify the destination base, given that the name and the creator are shown as unknown? I am seeking a solution within the Airtable UI or API ecosystem. Outside Airtable, I could message all base creators within the organisation, but t...
I asked Airtable support, and they asked some good, detailed, questions. These questions led me to check our code which produces the exported_at timestamps, and I found that the name of our column exported_to_airtable_at would actually be more accura...
The API call reported as succeeded, but the outcome appears to have failed. It’s the only one we noticed so far and not attributed to manual deletion or ‘something weird’ and moved on without investigating. The vast majority of our record creation ca...
I’m not so worried about why a record wasn’t created (and it may not be snapshot interference, that is just one suggestion). It’s that the create records POST call had a 200 response, and the number of records in the response object matched the numbe...
A screenshot of the Airtable snapshots on that day (British Summer Time), and of our separate record of the API POST call of the missing records (UTC). BST is 1 hour ahead of UTC.
