Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Scheduler Not Working For Short Periods

Go to answer
TracyGreen
Level 4

‎03-11-20 02:12 PM

Hello,
We've seen an issue a few times in the past week where the scheduler seems to just not schedule a process.  We have a process that runs every 5 minutes.  Yesterday, it finished one process at 2:37PM and then did not schedule the process again until 3:11PM.  It's like it gave the BOT a little break.

We have one license per resource machine and we only run one process at a time on each resource.  It doesn't seem like it could be a licensing issue. We have automatic archiving running, but it is not running on the BOT that had the issue yesterday.

Anyone have suggestions as to what this could be and how to fix it? 

Thanks.
Tracy ​

------------------------------
Tracy Green
Systems Developer III
Federated Insurance
America/Chicago
------------------------------
0 Likes
1 BEST ANSWER

Best Answers

Go to answer
Denis__Dennehy
Level 15

‎04-11-20 10:26 AM

Hi Tracy,  could you describe how your scheduler has been configured to start processes?   Why did you expect the process to start earlier than 3.11PM,  was it scheduled to start earlier?  What is the logic within your process to stop running at 2.37PM,  does it stop when it runs out of work?   
If you think there is a problem with schedules not starting (rather than a question about how schedules are configured), then what do the schedule logs say,  and what do the windows event logs on the Application Server for the times schedules failed to start?
Is your robot only working one process all day, irrelevant of the amount of work there is - if that is the case than the process should not be configured to stop when work runs out but instead poll all day.  However,  if the robot working a single process all day is inefficient (because there is not enough work for the entire day),  then consider working the process once or twice a day only (SLAs permitting) and moving onto other tasks or looking at the Dynamic Scheduler solution on the portal for ideas about how to build a more efficiant solution based upon work and priorities.

------------------------------
Denis Dennehy
Head of Customer Success, EMEA
Blue Prism Ltd
Europe/London
------------------------------

View answer in original post

0 Likes
1 REPLY 1

Go to answer
Denis__Dennehy
Level 15

‎04-11-20 10:26 AM

Hi Tracy,  could you describe how your scheduler has been configured to start processes?   Why did you expect the process to start earlier than 3.11PM,  was it scheduled to start earlier?  What is the logic within your process to stop running at 2.37PM,  does it stop when it runs out of work?   
If you think there is a problem with schedules not starting (rather than a question about how schedules are configured), then what do the schedule logs say,  and what do the windows event logs on the Application Server for the times schedules failed to start?
Is your robot only working one process all day, irrelevant of the amount of work there is - if that is the case than the process should not be configured to stop when work runs out but instead poll all day.  However,  if the robot working a single process all day is inefficient (because there is not enough work for the entire day),  then consider working the process once or twice a day only (SLAs permitting) and moving onto other tasks or looking at the Dynamic Scheduler solution on the portal for ideas about how to build a more efficiant solution based upon work and priorities.

------------------------------
Denis Dennehy
Head of Customer Success, EMEA
Blue Prism Ltd
Europe/London
------------------------------
0 Likes