Expose Configurable Timeout for Airtable Nodes?

Unfortunately, it appears the default Airtable node doesn't offer a configurable timeout setting. I'm uncertain about the default timeout duration for operations within this node type; I suspect it might be around 30 seconds.

Essentially, I've observed that when a callin.io workflow performs an Airtable Create or Update operation without providing an existing Airtable Record ID, and I have retries set to 3 times with a 1000 ms delay... Airtable API calls sometimes take longer than 30 seconds to finish...

So, when this occurs, callin.io interprets the timeout as a failure and attempts to RETRY the initial create operation (as anticipated). Subsequently, the SECOND retry is successful (again, as expected).

HOWEVER, the consequence I'm encountering is that because the FIRST attempt "timed out," callin.io incorrectly assumes the FIRST attempt was entirely unsuccessful. BUT, on the Airtable side, it DID succeed – it simply took longer than 30 seconds to fully process – and callin.io was unwilling to wait any longer.

Therefore, the side effect is that due to this default retry mechanism, I now have two DUPLICATE records created in Airtable.

The workaround would be to specify a longer configurable timeout within the Airtable node, but I don't see that option available. I believe if I could set a timeout of, say, 60 seconds or 120 seconds, then this type of side effect should be easily resolved going forward.

Does this explanation seem clear?