I have an automation that gets new cutsomers from an external system. It first GETs a complete list of customers, then loops though each, gets the customer detail and creates a new record in baserow.
It appears that the detail (single record get) from occassionally times out (set to 120), then the workflow continues and creates a duplicate record as the variables from the ‘last node’ (get detail record) haven’t actually updated. How do I get the workflow to either wait longer or identify and branch based on a timeout?
Hi @valsoar1 Unfortunately, we don’t yet have the ability to handle timeouts in order to use branching logic to take subsequent actions. I’ve created a feature request for this.
If manager.io supports data exports, an option might be to sync your data there to a Baserow table, that way you can completely avoid external API calls and associated timeout issues.
ok, understood. - here is what i have done for now (not particulary efficient). Conditional now compares the key from the iteration (loop) to that from the detail get node. If they match I create the record, if they dont (loop moved on but get timed out), I branch to an empty leg. Avoids duplicates, but now I have to have the whole automation run much more frequently - it eventually therefore creates all new customers but it’s inefficient. Would be nice if I could just draw a branch to loop back arond and retry the get until successful.