+46If there is an automation where a workspace with an automations writer, triggers a child workspace a number of times is it possible to restrict those jobs to run on the same engine without the use of a queue?
I want all child jobs triggered from the writer to run on the same engine as each other for a single automation run, but i don’t necessarily want to say that jobs can only be run on a single engine, as would be the case if I set up a queue.
+14Hi
If you do submit an idea, please share the reason why you need to do this and why queue control doesn’t meet the current need.
https://docs.safe.com/fme/html/FME-Flow/WebUI/Queue-Control.htm
Thanks!
+46I’ll add this as an idea as I’ve stumbled on the same issue again.
Basically I want to ensure that a workspace triggered multiple times by an automations writer waits for each job to complete so the workspaces are run consecutively and not in parallel. In a similar way to how the Workspace Runner has ‘Wait for job to complete’ option works.
I don’t want to simply assign these to a queue with a single engine as I want the first job to pick the first available engine.
