Error Running Scheduler: Timed out waiting for valid connection

[Anonymous]

Hy We are having problems running Schedulers. When we run a Scheduler, it is only executed in 3 terminals of the 8 assigned to it. These terminals assigned to this Scheduler are not running anything else. When we look Recent Activity, we can see the errors. Task: Consumers threw an exception: The given key was not present in the dictionary. Resource XXXXXXXXXXX1 : Timed out waiting for valid connection Resource XXXXXXXXXXX2 : Timed out waiting for valid connection Resource XXXXXXXXXXX3 : Timed out waiting for valid connection Resource XXXXXXXXXXX4 : Timed out waiting for valid connection Resource XXXXXXXXXXX5 : Timed out waiting for valid connection Anyone Know, why, we are having this problems? May it be a problem with sql ?

[Denis__Dennehy]

It looks like your application server (which kicks off the schedules at the correct time) is having trouble connecting to some of your resources. Many users seem to think that if they see Blue resources in control room everything is ok, but that is irrelevant - for schedules it is the application server that needs to be able to connect. You need to do some basic problem solving: What do the windows event logs tell you on the app server. Have you tested the app server connection to those resources. A knowledgebase guide asks the following questions: * Is publicly available (i.e. any user account can interact with it), * is currently running (blue icon in System Manager -> Resources) * that the Blue Prism Server can communicate with (note: this can be tested using the PING command and specifying the Resource PC's short machine name).

[ryanamiller]

Just curious, what version are you running? We're using 5.0.32 and we had this same issue. Found the following post and the workaround suggested by Alexander (last comment in post) worked for us: https://portal.blueprism.com/scheduler-timed-out-waiting-valid-connecti… I'm hoping you're also on version 5 and this issue isn't still present in version 6.