Configure multiple triggers for your Lakeflow Jobs in Databricks

Use cases

Imagine that you have a data engineering job that needs to run when a table is updated, but you also want to ensure a scheduled backup run. With this update, you can combine multiple triggers in the same job for different events.

• Combine different trigger types (schedule, table update, file arrival, model update, or continuous).
• Add multiple triggers of the same type.
• Pause and resume each trigger independently.

How to use

To configure multiple triggers using the Jobs API, use the triggers array inside JobSettings.

{
  "name": "my_job",
  "triggers": [
    {
      "schedule": {
        "quartz_cron_expression": "0 0 12 * * ?",
        "timezone_id": "UTC"
      }
    },
    {
      "table": {
        "table_name": "my_catalog.my_schema.my_table"
      }
    }
  ]
}

What happens in this code:

1. The name parameter defines the job name.
2. The triggers array groups the firing conditions.
3. The first object configures a schedule-based trigger.
4. The second object configures a table-update-based trigger.

Limitations and requirements

• The feature is in Beta.
• A job can have up to five active triggers.
• Continuous triggers cannot be combined with other triggers.
• A workspace can have up to 12,000 active triggers across all jobs, and paused triggers do not count toward this limit.
• Workspace admins must enable the Multiple Triggers setting from the workspace Previews page.