Skip to main content
Archived

Option that workspace can only be started if it is currently not running

Related products:FME Flow
  • March 13, 2018
  • 1 reply
  • 26 views

wicki
Contributor
Forum|alt.badge.img+10

For the workspaces published on the FME server, a setting would be good, with which you can choose that this workspace can only be started if it is currently not running.

So a parallel execution can be prevented.

Thus, when using multiple engines can be prevented that the workspace is carried out in parallel and thereby disturb themselves.

Even using just one engine, it may make sense to stop this process from queuing up.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

rylanatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • March 19, 2019

Related:

 

https://knowledge.safe.com/content/idea/38384/fme-server-gui-option-to-allowdisallow-concurrent.html

 

https://knowledge.safe.com/content/idea/54199/allow-to-define-maximum-instances-that-can-run-sim.html