Did this help you find an answer to your question?
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.
One way you could do it is by creating a Queue specifically for this workspace and then assigning it to one of your engines. Look under Engines - Queues - Create Queue. This way any jobs triggered to run this workspace will always go to the same engine and therefore will run one after the other, not at the same time.
Thank you both for your suggestion - this is a good solution although it's not perfect!
@virtualcitymatt "the downside here though is that if you are running a different job with that engine then the job will still be queued." -> That's true. My workaround for that is to divide the two engines: one engine for fast jobs, the other for time consuming jobs.
Hello!
We've got two Engines (FME Server 2020.1.0.1).
The workspace accesses files which could be accessed by only one editor. But the workspace can be started by many users.
How do I prevent running the same workspace at the same time on both engines?
The FME Server should detect whether the workspace is running. If the workspace is running, the new job shall be queued.
One way you could do it is by creating a Queue specifically for this workspace and then assigning it to one of your engines. Look under Engines - Queues - Create Queue. This way any jobs triggered to run this workspace will always go to the same engine and therefore will run one after the other, not at the same time.
Thank you both for your suggestion - this is a good solution although it's not perfect!
@virtualcitymatt "the downside here though is that if you are running a different job with that engine then the job will still be queued." -> That's true. My workaround for that is to divide the two engines: one engine for fast jobs, the other for time consuming jobs.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.