Schedule automations
Schedule automations to automatically run jobs for data extraction, data loading, or insight actions. You can specify an hourly, daily, weekly, or monthly recurrence for the running of automated jobs.
The frequency of a scheduled job determines the start time in relation to a fixed reference point within a specified time interval. All times are specified in UTC in 24h format, for example, 05/14/2021 1:23:08.
”Every 2 hours”: Counting starts at midnight, and then every second hour in the day.
“First day of the month every 3 months”: This could be a configuration appropriate for quarterly financial statements on April 1, July 1, October 1, and January 1.
For daily scheduling, counting starts on the first day of the month and continues until the end of the month.
Suppose today is Thursday, February 26, 11:00 a.m. February has only 28 days. Let us schedule an automation at 6:00 a.m. with each of the following rules:
Runs every day: Next run Friday, February 27, because 6:00 a.m. has already passed.
Runs every 2 days = 1st, 3rd, ... 27th day: Next run Friday, February 27 (same next execution time as when scheduling every day)
Runs every 3 days = 1st, 4th, ... 25th, 28th day: Next run Saturday, February 28
Runs every 4 days = 1st, 5th, ... 25th day: Next run on the first day of the next month: Sunday, March 1
Runs every 5 days = 1st, 6th, ... 26th day: Next run on the first day of the next month: Sunday, March 1
The same applies to every interval longer than 5 days, because the end of the month is always exceeded in this case, and counting days restarts at 1.
Click Automation in the Data set panel. The Automation section opens.
Click Add automation.
Enter a name for the automation.
Click Add. The page to configure an automation opens.
By default, the start time is preset to "every day at 12:00 AM", and the automation job mode Run all is selected. This means that all available jobs are run daily at 12:00 a.m.
Click Configure to schedule the automation. The Configure schedule dialog opens.
Specify the recurrence interval and the time at which the jobs are to be run. Depending on the recurrence interval you select, for example, daily or weekly, different options are available.
All options marked with a red star must be specified.
Click Apply.
You scheduled the job automation.
Example
Specify the automation job mode. By default, Run all job mode is selected. That is, all available jobs are run with the automation. You can select specific jobs to run if you do not want all available jobs to be run.
The order of the jobs is fixed. This means that all data extraction jobs are run first, then all data is loaded, and then insight action jobs can be run.
Click Custom. More options to configure the automation jobs are displayed. You can configure jobs for Extractions, Data load, and Insight actions.
Example
Enable the jobs, you want to run, for example, extractions or insight actions. A dialog opens for selecting the jobs.
Select Extract all to run all extraction jobs or select Trigger all to run all insight trigger with the automation. All extractions or insight trigger that exist at the time when the automation is started are included in the automation. If extractions or triggers are explicitly selected and they do not exist at the time, they are ignored.
Note that a data load job does not automatically trigger an insight action job (as in previous ARIS Process Mining versions).
Example
Two jobs to run insight actions are selected.
Click Apply.
Job automation is configured and scheduling is enabled by default.
To deactivate the automation, disable the Enable schedules option. Your settings will be retained.
To start the automation manually, click 
Run now. The automation starts immediately (if no other process is currently running) and its status is displayed in the Run log section. A manually started automation is listed as ad-hoc run: <name of the automation>.
You can manage automations on the Automation page.
The automation runs every two months on the first Monday at 12:00 p.m. and includes all available extractions, data loading, and one selected insight action.
