Skip to main content
Open

Skip automation trigger if it is already running

Related products:FME Flow
danilo_fme
vxn43
deanhowell
jelle
jasperwis
+9
  • danilo_fme
    danilo_fme
  • vxn43
    vxn43
  • deanhowell
    deanhowell
  • jelle
    jelle
  • jasperwis
    jasperwis
  • sionejw
    sionejw
  • mholemans
    mholemans
  • chk1
    chk1
  • carlm
    carlm
  • margotdh
    margotdh
  • becchr
    becchr
  • sammy
    sammy
  • carolinev
    carolinev
  • raghavendrans
    raghavendrans

becchr
Influencer

In automations, for the action “Run a workspace”, there’s a ‘Skip if Job In Progress’ option, I think a ‘Skip if Automation In Progress’ on the level of the automation itself would be very useful!

 

The purpose of this option would be to prevent the same automation from being initiated again if a workspace from that automation is currently still running or queued. This could help prevent unnecessary duplication of processes and especially potential conflicts.

 

We have some complex automations we really want to avoid to be run in parallel, but at this moment we don’t have an easy or nice solution for that...

 

 

 

3 replies

nordpil
Supporter
Forum|alt.badge.img+11
  • Supporter
  • April 22, 2024

I have implemented this in the past with a simple workspace to check currently running and queued jobs (using REST API) - and put that workspace as an action right after the automation trigger. In my case we’d wait for all other jobs to finish (so my ‘wait/check’ workspace would hog an engine) and then proceed. One can also consider just terminating if it is already processing.

 

like the first comment on this topic:

 


LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • July 10, 2024
NewOpen

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • April 5, 2025
This is related to https://community.safe.com/ideas/disable-same-workbench-ability-to-run-simultaneously-31793

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