Workflows, schedules, and activity
Orchestration workflows covers what DeltaVault generates and how you edit it. This guide covers the three screens where you watch it: Workflows, Schedules, and Activity.
All three carry a Preview badge in their header. They are released to organizations enrolled in preview access, so if yours is not enrolled they do not appear in the navigation rail, and opening one directly takes you back to your dashboard.
Workflows
Section titled “Workflows”The workflow list is the inventory of every workflow in your organization, nested so a master workflow holds the layer workflows it chains. Its columns are:
- Name, which expands to show the workflow’s children.
- Comment, your own note on the workflow, or
-. - Schedule, which names the schedule the workflow runs on, or
-. - Project, when you are looking across the whole organization rather than from inside one project.
- Generated, which carries a Generated badge on every workflow DeltaVault produced and stays blank on the ones you created yourself.
That Generated badge is the answer to “where did this come from”. Select any row to open the workflow on its designer canvas, which Orchestration workflows walks through.
Two actions sit in the header. Generate from project… rebuilds a project’s workflows and shows you a preview before anything changes. New creates an empty workflow by hand. Each row’s menu offers Edit and Delete.
Both header actions, both row actions, and the bulk Delete are disabled while you are on main, with the tooltip Read-only on main. Switch to a branch to edit. Switch to a branch to use them.
Before you have any, the page reads No workflows yet and offers New.
Schedules
Section titled “Schedules”A schedule is a name, a type, and a cron expression, and the list shows exactly those three: Name, Type as a badge, and Cron Expression, which reads - when the schedule has none.
New opens Add Schedule, which asks for Name, Schedule Type, Cron Expression (for example 0 2 * * *), and Timezone, which defaults to UTC when you leave it empty. Each row’s menu offers Edit and Delete. Before you have any, the page reads No schedules yet.
Schedules are yours alone. Generating a project’s workflows never creates one, changes one, or attaches one. Every row on this page is a row somebody typed.
Activity
Section titled “Activity”Activity is the record of everything that changed in your organization, newest first, grouped by day.
Two controls narrow it. Time covers 24h, 7d, 30d, and All, and starts at 7d. Action is a row of seven chips, Create, Update, Delete, Branch, Commit, AI, and Migrate, all selected when you arrive.
Each entry names who did it, what they did, and the thing they did it to, with the time on the right and a badge naming the branch when the change did not happen on main. Select an entry to expand it: changes to a record show you which fields moved, from what to what.
Two states look empty for different reasons. Untick every chip and you get No action filters selected, because nothing was asked for. Leave the chips alone and you may still get No activity in this range, in which case widen the Time control.
One behavior to know before it surprises you: workflow generation entries appear only while all seven chips are selected, and they read workflow_generate rather than a phrase. Untick any single chip, even one unrelated to workflows, and they drop out of the feed until you tick it back.
Where a generated job shows up
Section titled “Where a generated job shows up”Generation writes workflows, and only workflows. Tracing one through these screens:
- Workflows lists it with the Generated badge, under the master workflow that chains it.
- Schedules does not change at all, because generation creates no schedule.
- Activity records it, subject to the chip behavior above.
The deployable job definition itself is not on any of these three screens. It is a file in the build, databricks/resources/workflows.yml, and you read it in the artifact tree on The Builds page or from your project’s Build tab.