the downside here though is that if you are running a different job with that engine then the job will still be queued.
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.