Scheduler

The primary way of executing processes in production is through a scheduled execution. Our scheduler has couple of different ways of executing the process:

• One time – used when you just to need to execute process at specified date/time.
• Recurring – used when you need to execute the process multiple times. There are several options of recurring schedule:
  • One time per day – you can specify the time and on which days of the week you need to run the process.
  • Multiple times per day – you can specify the time interval (like every 2 hours), limit the interval by specifying from which hour to which hour and select the days of the week when the process needs to run.
  • One time per month – you can specify on which exact day in the month or week of the month you need to run the process and during which months. For example, you can say run this process on Monday of the second week of January, February, and March.

When the schedule is created Headquarters will create the jobs for the robots and make sure that the robots execute them. Jobs created from schedules can be seen in Active Jobs and Completed Jobs lists available from the main HQ navigation.

Scheduler has additional options and functionalities which are important:

• Priority – determines the priority of the jobs that will be created from this schedule. Higher priority jobs will get executed faster than lower priority jobs.
• Schedule validity – limits the time span during which the schedule is used.
• Timeout in minutes– determines the number of minutes that HQ will wait for the process to get executed by the bot. If that timeout is exceeded the job will go to cancelled status.
• Job execution timeout – defines the maximum execution time for the process. For example, when set that the process can last for max one hour. This prevents the process that is somehow stuck to keep the bots occupied even though it’s idling.
• Retry attempts – if the process fails, we can set how many times the robot will try again.

To prevent unfinished jobs in case of GateKeeper failure, we have implemented a new rule that automatically aborts the process once the GK is up. Additionally, please note that if your job remains in a running status for 24 hours, it will automatically be marked as aborted to prevent the unnecessary consumption of license hours.