I have been thinking that it was a bit of a mistake to restrict machines to running only one process at any given time, and I am wondering if it possible for you to re-implement this in some form. Here are my reasonings for this:
I understand that you want to prevent misuse of licenses, however, the main strength of UiPath is the simulation of user actions in Windows/Citrix etc…Therefore, if people are using UiPath to simply run hundreds of tasks, they could probably just do this using other scripting tools such as Powershell. At least they are using UiPath in this case.
It remains annoying that you couldn’t run a non-interactive load process for back office automation. Now we are forced to find workarounds which effectively does the same thing but is less impressive. For example, you cannot run constantly in the background checking every 5 minutes for some activity such as a new email in the Inbox.
When considering Front Office automation, this restriction could have a huge impact. Rather than running multiple processes simultaneously whether they be email generation or simulating activity with an application, we are forced to run things sequentially. This obviously means the overall time is far greater and the impact of FO automation is not as impressive.
Happy to hear your reasons for not doing this but thought it was worth raising. I really don’t think the concerns over misuse are valid but I may be wrong. Perhaps you could restrict to 3 processes to make this more reasonable?