Understanding Clay Rate Limits with Airtable Integration

Hi Everyone - I am using Clay with the Airtable integration (not Web Hook). A new record in Airtable triggers a Clay run. Are there Clay rate limits in place to prevent the action of a row completion from returning the updated content to Airtable with the same Airtable Rec_ID? The process flow also includes n8n, outside of the Clay/Airtable integration. Thank you!