Aug 06, 2024 11:38 AM
I am looking into the possibility of using AirTable as a back end data repository for some of our data. In order for this to work, I'd have various event triggers accepting data fields and using that data to create or update an Airtable base/table using REST API calls. The goal is to replace some existing back-end that is stored in a SQL Server database.
One aspect that I'm not sure to handle is preventing concurrent changes. If, for example, I have multiple changes happening to a record that could possibly be processed at near the same time, I need to make sure that the newest value "wins".
The way this works in the current service is as follows:
I realize that Airtable doesn't have direct analogs to everything that can be done with a SQL database. I'm wondering what the best practice would be with the Airtable API if I want to manage concurrent modification scenarios like this one.
Aug 06, 2024 11:41 PM
Hello @TimothyMDean,
First, read this https://support.airtable.com/docs/managing-api-call-limits-in-airtable#:~:text=Airtable%20enforces%2....
Then read this https://airtable.com/developers/web/api/errors
If you still has issues about how those ratelimit and errors are works. then comeback again with screenshots and request information.
👍
Aug 08, 2024 11:51 AM
@dilipborad Sorry - those links don't answer my question. This isn't a rate limit issue, it's a question about how possible concurrency issues are handled by the API.