Check the concurrency limit for each server when manually running a multiplexed event

[Jacketbg]

This is a bit hard to explain, but I'll try my best.
It's again related to "persistent jobs" (#190). I have few events that run on 10 separate servers in multiplex. They are singleton events, so each servers should always run only a single job at any given time. Sometimes one server crashes or something else happens and the job is no longer running there, but is running on all other servers. Here's how it looks:

The first event is now running on only 9 of 10 servers. If click Run I receive the following error:

So now to start the even on this servers I have to manually abort the other 9 jobs, which is tedious. I found that disabling the event gives me an option to abort the currently running jobs (which is nice!), so this saves a bit of time. After all servers abort their jobs, then I can run them again. This is not very optimal. It's also intrusive to the system, especially if the scripts have a failover role.

Is it possible for the Run action to actually check if the event is multiplex and go through each server and apply the concurrency limit per server?
Thanks!

[jhuckaby]

Thank you for the issue report. I believe I understand what you are saying. I will try to come up with a solution to this, but I can't give an ETA.