Hi everyone,
I think a new action “delay” (like the Decelerator transformer) would be a good addition to automations.
My current scenario:
Data is inserted into an external system and I need to check via HTTP calls if the external system has processed the data yet. I don’t want to do this check in the main Workspace, since the external system can take between 1 and 30 minutes.
I’ve solved this for now using the Workspace Retry in automations. However, this results in a unpleasant Job history, since I need to design the Check-Workspace to run into an error to trigger the retry. A delay would allow me to loop back to a Check-Workspace on my own terms.
I’m sure there are plenty more use cases where a delay could be useful. Especially in combination with loops. What do you think?
Kind regards
Dennis
