[PoolName] is too busy to run that process

[PatrickOttery1]

Hi all, Since upgrading from v5.0.23 to v5.0.30, we€™re having issues utilising pools correctly within Blue Prism v5.0.30 No matter how many resources are assigned to a pool, we can only ever utilise the first resource in the pool. e.g. Pool1 contains resources 1,2,3,4,5 Process A is scheduled on Pool1, which farms the process out to resource1. If Process B is then scheduled on Pool1, I expect Blue Prism should farm the process out to resource2, however, we receive the error message €œPool1 is too busy to run that process€ This eliminates all benefits of having a pool in the first place and forces us to manage our schedule carefully to avoid conflicts, as a process will not execute at all if the pool is busy. It€™s difficult to state with complete certainty that this is caused by the Blue Prism v5.0.30 upgrade, however, when looking at control room for processes assigned to a resource pool, we can only see the first machine in the pool utilised and no overlap times. I have attached an image of the error message. If there is any further infomration which I can provide to assist with diagnosis, please let me know. Regards, Patrick.

[Denis__Dennehy]

I think this would require some experiementation from your Application Server machine to figure out what is happening (it is from the App Server that Schedules instigated on the pool). When this issue occurs can you manually start the same process on the resources within your pool or are they showing as busy or are there any connection issues?

[PatrickOttery1]

Hi Denis, When this issue occurs, I cannot manually start the process on the individual resource, as it's not available unless I take it out of the pool. If I take the resource out of the pool, then yes, I have no trouble starting the process on an individual resource. Can you please elaborate on the experimentation I might undertake on the Application Server? Thanks for your time, Patrick.

[John__Carter]

Hi Patrick - probably you've already checked, but look at all the resources in the pool and confirm that there are no old pending sessions. Control room defaults to showing 'today' and hiding pending sessions created earlier.

[PatrickOttery1]

Hi John, Correct, there are no pending sessions. We've raised an official support ticket, so I hope to get a resolution there. Regards, Patrick.

[John__Carter]

Hmm weird, see what our support guys suggest then. Maybe also try creating a brand new pool so see if that behaves differently to one that existed before the upgrade. I can't see that it would, but worth a quick test.

[NitinKamurlekar]

This is happening to me today after we upgraded to 5.32. i was expecting new features but it took me back to square. Sad there is no documentation on prerequisite and FAQ on the errors. Were you able to fix this problem?

[SamanthaShaw]

To those experiencing this issue - are you using Single Sign-On to authenticate with Blue Prism?