Skip to main content
Open

Decelerator / Delay Action in Automations

Related products:FME Flow
  • February 24, 2025
  • 1 reply
  • 75 views
geomancer
danilo_fme
davtorgh
spatialexjames
mikev
+3
  • geomancer
    geomancer
  • danilo_fme
    danilo_fme
  • davtorgh
    davtorgh
  • spatialexjames
    spatialexjames
  • mikev
    mikev
  • mmccart
    mmccart
  • p.jeremie
    p.jeremie
  • mark2atsafe
    mark2atsafe

denniswilhelm
Contributor

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

1 reply

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • April 29, 2025
NewOpen

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings