topic I have observed that if a in Product Forum

Scheduler not Started as Scheduled

Anonymous — Mon, 16 Jan 2017 18:28:00 GMT

Hi All, We have investigated an issue on BP scheduler and identified that one of the robo did not start the process as scheduled for "Daily" Basis. Please let me know what needs to be done so that this error can be avoided.

I am sure that your answer

TimMorthorst1 — Tue, 17 Jan 2017 15:35:00 GMT

I am sure that your answer will be here: https://blueprism.knowledgeowl.com/help/what-are-the-requirements-for-r In general, make sure that the scheduler is initiated by an application server.

Interesting , we are having

Stephen.Jones — Mon, 23 Jan 2017 13:50:00 GMT

Interesting , we are having the same problem with just one of our robots. The schedule had been running fine upto 18/01. SInce this date the schedule hasn't run. I've run through the checklist on the FAQ and it appears ok. I'm thinking about restarting the application server , BUT i've never done this. I know when you restart the robots you need to run the Blue Prism - Resource PC. Do i need to do something similar on the application server ?

I have observed that if a

SimenAakhus — Fri, 27 Jan 2017 15:22:00 GMT

I have observed that if a Schedule terminates, it will fail to launch on the next run. I always have to manually reset the schedule. I am not sure if this is a v5.0.23 bug... - Simen

Thanks for the info, one part

Stephen.Jones — Mon, 30 Jan 2017 21:06:00 GMT

Thanks for the info, one part of the schedule has been designed to terminate if there are no jobs in the queue. I wonder if we are having the same problem. I'm getting the developer to change the process to not end in a termination as good practise anyway. This may fix the schedule problem for us.

I am facing same issue in 5.0

Anonymous — Tue, 01 Aug 2017 14:46:00 GMT

I am facing same issue in 5.0.24 version where scheduler is not working for few robots. We are running them manually. Can someone please help here. Error messages I am receiving - 1. No sessions were successfully created. 2.The given key was not present in the dictionary. 3. Timed out waiting for valid connection.