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.