It happens frequently that we would like to ensure that a workspace in FME Server runs only once or want to limit a workspace from taking all resources. Tagging engines is useful but is limited and in most cases doesn't deliver the real optimal result. If workspaces or repositories would have the advanced option to define the maximum instances that can run simultaneously or/and the option how long they can stay in the queue a lot of these weaknessess could be removed.
Archived
Allow to define maximum instances that can run simultaneously
+3This 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.
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.
+14- Safer
Related:
https://knowledge.safe.com/content/idea/38384/fme-server-gui-option-to-allowdisallow-concurrent.html
https://knowledge.safe.com/content/idea/65826/option-that-workspace-can-only-be-started-if-it-is.html
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.