Lakeflow Jobs
A Lakeflow job can now carry up to five triggers.
What Beta promises
Open to most customers but not for production: support runs through engineering, and the shape of it can still move. On by default on Premium, off on Enterprise.
| Who can use it | Most customers |
|---|---|
| Production use | No |
| Support | Engineering only |
| On by default | Premium yes, Enterprise no |
The definitions are Databricks' own, on its release types page. The label on this page is the one the feature's documentation states, last checked on 7 Oct 2026.
Where to read more
It is part of something we wrote up: Triggers: schedule, file arrival, table update, continuous — A job can start on a schedule (Quartz cron), when files land in a volume or external location, on a Unity Catalog table commit, or run continuously. Time-based vs. data-driven is a favorite exam question.