While a Run time Resource is busy running a process it own't take another one. It will be a nice functionality if Que concept is introduced in Product. That way it will execute on First in First Out basis.
I think I was asking about process level. If Run time Resource is busy running one process and user wanted to drop another process on that Run time it doesn't take and throws and error "Resource is Busy running another process ".
Do you mean, that pending sessions should be queued and as a resource gets idle Blue Prism automatically starts the next pending session? The thing is: As far as i know a pending session is also consuming a license. Maybe that point should be checked too.
I think what Menas is asking for is the ability to queue up sessions, so that if the resource is currently occupied, you can still create a 'waiting to start' session that will run once the current session ends.
There are no plans to introduce a queuing concept to Blue Prism Enterprise runtime resources, so I've gone ahead and marked this idea as Not Planned.
In the very near future, we'll be releasing our Powered by Next Gen orchestration service, which will allow users to promote their runtime resources to hybrid digital workers who can in turn have queued sessions to allow for more robust orchestration - this would be the way to access the enhancement that your original idea describes.
Regards,
Rob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
