My scheduled airtable source is stuck - The blue info box has shown a spinning circle for multiple weeks now and many of the airtable records are missing. It seems as though the sync will not complete. I have attempted to reauthorize the airtable connection, but no luck there.
It seems you're experiencing an issue with your Airtable sync. This could be due to various reasons, such as field name mismatches or connectivity problems. Here are some steps to troubleshoot: 1. Double-check field names: Ensure the field names in Clay exactly match those in Airtable, including capitalization. 2. Verify all fields are visible: Sometimes, not all fields from Airtable appear in Clay. Make sure all expected fields are visible in the import options. 3. Retry the sync: If you haven't already, try disconnecting and reconnecting your Airtable integration. 4. Check for any error messages: Look for specific error notifications that might provide more details about the sync issue. If these steps don't resolve the problem, can you provide more information about any error messages you're seeing or specific fields that are missing?
Hi Mark, thanks for your message. Airtable records are pulled into Clay in bulk every 24 hours after the initial setup. The issue is with Airtable's API rates and there's unfortunately not much Clay can do here. A possible workaround for this issue is to set up an HTTP API call to the Airtable endpoint you're targeting, and retrieving records on a rolling basis using our webhook table. This video shows you how to create a webhook table within Clay. I hope this was helpful. If there's anything else I can assist you with, please let me know!
Hi Bruno - I'm not sure that makes sense. I can understand that there might be a functional limit on the number of records that clay could retrieve based on Airtable
I can understand that there might be a functional limit on the number of records that clay could retrieve based on Airtable's rate limits. But how can I be sure this is a result of a rate limit and not something else entirely? The status message on the source doesn't give any information about what's going on, how many records have been pulled, the percentage of total records that have been, when it the update was started, or when the last update finished. How can I be sure that something hasn't broken completely? If there is a maximum number of records for an airtable source, can I know what that limit is so that I can stay below it? Airtable says "there is a limit of 50 requests per second for all traffic using personal access tokens from a given user," so realistically I can't see why my airtable base of around 3500 records would cause the source to run indefinitely
Mark - Sorry for this, it looks like something may have gone wrong in the importing process here. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Thanks for your patience. I’ve confirmed with our engineering team that this issue has been added to our backlog. For context, our product team prioritizes bugs based on severity and how many users are affected, so this may take some time to address depending on other ongoing work. I’ll go ahead and mark this as closed for now, but I’ll follow up as soon as there’s an update. If you don’t hear from me, the team is still working on it and this thread will reopen automatically when there’s news. Any questions before I step away for now?
.png){kind=logo}
