https://community.blueprism.com/t5/Product-Forum/Scheduler-triggered-a-process-and-left-it-on-a-pending-state/m-p/84381#M35527 The scheduler triggered the login agent process on control room and created a pending session, but never put the process on the running state. When the same process was tried to be triggered through scheduler today, it kept failing with the error reason "Resource PC is too busy to run that process"; whereas it was the scheduler itself which had kept the process in pending state. Fri, 26 Jan 2018 16:51:00 GMT Anonymous 2018-01-26T16:51:00Z https://community.blueprism.com/t5/Product-Forum/Scheduler-triggered-a-process-and-left-it-on-a-pending-state/m-p/84381#M35527 The scheduler triggered the login agent process on control room and created a pending session, but never put the process on the running state. When the same process was tried to be triggered through scheduler today, it kept failing with the error reason "Resource PC is too busy to run that process"; whereas it was the scheduler itself which had kept the process in pending state. Fri, 26 Jan 2018 16:51:00 GMT https://community.blueprism.com/t5/Product-Forum/Scheduler-triggered-a-process-and-left-it-on-a-pending-state/m-p/84381#M35527 Anonymous 2018-01-26T16:51:00Z https://community.blueprism.com/t5/Product-Forum/Scheduler-triggered-a-process-and-left-it-on-a-pending-state/m-p/84382#M35528 Knowledgebase search: https://portal.blueprism.com/customer-support/knowledge-base/why-are-so…   Sun, 28 Jan 2018 15:15:00 GMT https://community.blueprism.com/t5/Product-Forum/Scheduler-triggered-a-process-and-left-it-on-a-pending-state/m-p/84382#M35528 Denis__Dennehy 2018-01-28T15:15:00Z https://community.blueprism.com/t5/Product-Forum/Scheduler-triggered-a-process-and-left-it-on-a-pending-state/m-p/84383#M35529 @Denis__Dennehy, the schedule included only one Run-time Resource on which multiple processes were to be triggered sequentially. The knowledge article mentioned by you should not possibly be the reason why this issue might have occurred, since the Resource had been 'Connected' and only due to which it could create a pending session. Also, the scheduler never failed. It was still in the running state with blue play icon and the status did not change until the pending session was deleted. After the session was deleted, the logs were inaccessible. When I had checked the logs before deleting the session, it indicated that it was on the 'Set Windows Login' process and had been like that for hours. Can anyone provide any more details on that? Mon, 29 Jan 2018 14:29:00 GMT https://community.blueprism.com/t5/Product-Forum/Scheduler-triggered-a-process-and-left-it-on-a-pending-state/m-p/84383#M35529 Anonymous 2018-01-29T14:29:00Z