+2Ik have one job running and then started a second job manually.
However for some reason the second jobs keep waiting.
The both run on the same execution server but why does not it start a second job. Is there a setting which prevents the second job from starting or happens this only if you start multiple jobs manually?
Best answer by Christian Hauggaard
Hi
Currently a VM running the execution service can only run one MDW/SSL job at a given point in time. If you have multiple MDW/SSL execution servers, each with different instances selected in the Execution Server Configuration tool, then multiple MDW/SSL jobs can run concurrently.
+2<was for another ticket>
+5Hi
Currently a VM running the execution service can only run one MDW/SSL job at a given point in time. If you have multiple MDW/SSL execution servers, each with different instances selected in the Execution Server Configuration tool, then multiple MDW/SSL jobs can run concurrently.
+2Hi Christian,
Thanks for the answer.
In the legacy version you could have concurrent executions so more executions could run simultaneously.
Do you know it is on the wishlist to be made possible ?
+2Hi team,
Be sure to thumbs up and comment on this Allow multiple jobs to be run concurrently | Community (timextender.com).
Kind regards,
Andrew
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
