The Robot Schedule AUTOWORK program allows you to run jobs that were missed while Robot Schedule was inactive. AUTOWORK uses available completion history when determining missed jobs. It does not consider purged history records. Therefore, jobs may appear as “missed” even if they ran.
You can schedule the program in a Robot Schedule job or call it from a command line.


Use the following command to call the AUTOWORK program from a command line or Robot Schedule job. The program has two parameters that will determine which missed jobs to run.


  1. The first parameter is date, where date is when the jobs were missed. Enter the date in your system date format. This parameter is required.

    If using AUTOWORK in a Robot Schedule job, you can use the reserved command variable @@DATE to supply the current system date at job run time.

    Note: You must include the single quotes (' ') around the date, whether you enter the date or use the @@DATE reserved command variable.

    The date you enter determines the jobs that will run:
  • Todayʼs Date - If you enter today’s date, Robot Schedule runs missed jobs that were scheduled from midnight (00:00) to the current time.
  • Earlier Dates - If you enter an earlier date, Robot Schedule runs missed jobs that were scheduled from midnight (00:00) to 23:59 on that date only. It does not run missed jobs from any other date. If you need to run missed jobs for more than one date, enter each date separately. Note: AUTOWORK relies on completion history to perform an accurate check. Purged history records can make a job appear to have been “missed” when it actually ran.
  • Multiple Runs - If a job is scheduled to run at more than one time on the date you specify, Robot Schedule runs each missed job only once, even if it has missed more than one run time. If a job with multiple run times has completed once successfully on the specified date, it's not listed as “missed” and AUTOWORK does not run it again.
  1. The second parameter is an optional parameter.  This parameter is defined as a 1 byte character and informs the process what level of Completion History to inspect when determining if a job has been missed.
  • ‘Y’ - Ensures the process inspects all existing Completion History for the specified date to determine if it was missed.
  • Not passed - Informs the underlying process to only inspect Completion History for days within the current week (Monday-Sunday) when determining if a job is missed.  This scenario is how the program previously worked.


Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case