Schedule Jobs

1. Go to a project.
2. From the navigation pane, click Jobs > Schedules.
3. Click Schedule a Job to open the Create a Scheduled Job page.
4. 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. Data Plane & Hardware
   Select the Hardware Tier used by the Job. The same tab lists the Datasets and NetApp Volumes the Job mounts, in a table with Storage and Snapshot columns. Pin an asset to a single snapshot from the Snapshot column. Choose a snapshot per asset at launch covers the options. Environment
   Select the compute environment used by the Job. Optional: Select the Environment revision. By default, Domino uses the latest revision of your Environment when the Environment starts.
   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.
   You can also configure your Job to create Snapshots of Datasets it mounts upon execution completion. This feature requires AllowDatasetSnapshotsOnExecutionCompletion to be enabled. See the create a snapshot guide for more details. A Dataset pinned to a single snapshot mounts read-only, so a completion snapshot of it captures no changes.
5. 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
6. Set up the schedule. Use custom expression
   Enter a custom Quartz CronTrigger expression. For example, if you want to run the Job on the fifth minute of every day, enter the following:
   `0 5 * ? * *`
   
   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.
7. Set up any additional actions: Notify emails
   Enter a list of email addresses to notify when the Job is completed. Update Domino endpoint
   If a Domino endpoint has been published from the project, the selected Domino endpoint is republished after the Job has been completed. Use this for retraining and updating a Domino endpoint regularly.
   In restricted Projects, scheduled Runs use the current restricted revision of the Environment selected for the Job. This revision may be different for a scheduled Run from the revision used in a previously scheduled Run.

​

Manage scheduled Jobs

​

Next steps

• Monitor and view Job results.
• Automate complex pipelines with Apache Airflow or Kubeflow.