Hello Ladies and Gentlemen, I am having a problem updating a record in my airtable node. It keeps saying I have hit rate-limits. I added a wait node to it and this has kept repeating. What do I do? . I have attached my workflow and the error message gotten.
@brickelsmart that error means you tripped airtables 5-requests-per-second cap, and the catch is airtable then locks you out for a full 30 seconds after. your node is set to auto-retry (you can see “this node will automatically retry if it fails”), but n8ns retry wait is way shorter than that 30s, so every retry fires while youre still locked out and fails again, which is the loop youre stuck in. fix is on the Update record node, Settings, Retry On Fail, set Wait Between Tries to 30000 (30s) and Max Tries to 3, so the retry only lands after the lockout clears. your 4-minute wait already spaces the updates fine, its the retry timing thats actually biting you.
@brickelsmart youre right, n8n caps that field at 5s, so the built-in retry cant outwait airtables 30s lockout, it just burns 5s tries inside it. better to turn Retry On Fail off and handle it in the flow instead, set the Update node On Error to Continue, route the failure into a Wait 30s node, then loop that back into the update. but with a 4-minute wait between updates you really shouldnt be hitting 5/sec from this node alone, so somethings else tripping it, are you re-running this workflow a lot while testing, or is another workflow hitting the same base? airtables limit is also 50 requests/sec across all bases on one token, not just per base.
Yeah, that’s the strange issue. All other workflows I have that have airtable are unpublished. But let me recheck again carefully.
