You can schedule Jobs in advance and set them to execute on a regular cadence. These can be useful when you have a data source that is updated regularly.

To schedule a Job:

Go to a project.
From the navigation pane, click Jobs > Schedules.
Click Schedule a Job.
In the Create a Scheduled Job page, define the job:
Scheduled Job Name

Enter the name of the job. The Jobs Dashboard lists each job by this name.

Branch or Commit Id

In a Git-based project you can specify a branch or commit ID when launching or editing a job.

File Name

Enter the name of the file to execute. Include any optional arguments to pass to the file.

Hardware tier

Select the hardware tier used by the Job.

Environment
Select the compute environment used by the Job.

Optional: By default, the latest revision of your environment is used when your environment starts. To use another revision of the environment:
In the Environments section, click Change.

A list of revisions for this environment opens.

Click the revision number of the environment you want for your job. The revisions you selected displays in the Revision section.

Note
Domino recommends using the revision set as the active one by the project owner. If you select a different revision, the Not Recommended warning is shown.
Data

Click to expand the section to see the Datasets configuration used by the Job.
Click Next. Then, select and define the compute cluster.

The configuration options for each cluster type are explained here: Spark Cluster Settings Ray Cluster Settings Dask Cluster Settings MPI Cluster Settings
Click Next and set up the schedule.

Use custom expression

Enter a custom Quartz CronTrigger expression. For example, if you want to run the job on the 5th minute of every day, enter the following:

0 5 * ? * *

Note
To learn more about these expressions, see CronTrigger expressions.

Repeat every

Set the frequency at which you want the Job to repeat.

Run sequentially

When you set a job to run sequentially, the scheduler always waits for the last job it started to complete before starting the next one. For example, if you set up a scheduled job to run once per hour, and one of the jobs launched by the scheduler takes 90 minutes to complete, the next hourly job does not start until the previous one has finished. Otherwise, multiple jobs from this scheduler are allowed to run simultaneously. The scheduler does not wait for the previous job to finish if it’s still running. This mode should be used when your job doesn’t depend on output from the previous Job.
Click Next. Set up actions, if any:

Notify Emails

Enter a list of email addresses to notify when the Job completes.

Update Model API

If a Model API has been publishing from the Project, the selected Model API will be republished after the Job has completed. Use this for retraining and updating a Model API regularly.

Scheduled Jobs