cancel
Showing results for 
Search instead for 
Did you mean: 
NicholasRobbins
Level 3
Status: Not Planned

​When scheduling an automation to run at a specific time, if the pervious scheduled process overlapped, due to it not completing before the next scheduled automation, then the system never goes back to restart the second automation. It only shows in the Recent Activity log. It should try again.

2 Comments
chris.strong
Staff
Staff

Hello @Nicholas Robbins Leon

 

I realise this one has been hiding in the list for a long time, I’ve updated the status to Reviewed, which means that we understand the ask and continues to allow other Community members to vote for and comments on the request.

 

Kind regards

Chris Strong

Senior Product Manager

SS&C | Blue Prism

Status changed to: Not Planned

Hello @NicholasRobbins,

Thanks for taking the time to raise an idea.

The Blue Prism Enterprise scheduler currently expects all runtime resources required in the execution of a scheduled task to be available at the time the task is triggered else the schedule will not run. As things stand, there are no immediate plans to change this, so this idea is going to be marked as Not Planned.

As an aside, we will shortly be releasing our new Orchestrate RPA capabilities alongside Blue Prism Enterprise 7.4 which will allow users to promote their runtime resources to hybrid digital workers, which will then be able to leverage our Powered by Next Gen orchestration services for the scheduling of work. These scheduling mechanisms (called Automation Flows) are much more tolerant of things like resource availability, effectively queuing sessions for later assignment if things are occupied at the elected trigger time.

Let me know if you have any further questions.

Regards,

Rob