A workflow holds the schedule and settings for the work it runs: loading a data source's tables in the Lake, running Warehouse transformations, or pushing Writeback tables to a destination. Use this page to add a workflow, change its settings later, or delete one that no longer has tables or transformations assigned.
| Setting | What it does | Default |
|---|---|---|
| Datasource | The source or Writeback destination the workflow belongs to. It cannot be changed after creation. | None. Choose one. |
| Workflow Type | Standard or Snapshot. It cannot be changed after creation. | Standard |
| Workflow Name | The name of the workflow. It must be at least 2 characters long and unique. It cannot contain the words standard, snapshot or replication. | Empty |
| Batch Size | How many nodes of one run may work at the same time. Enter 1 to 100. | 10 |
| Restart Count | How many times DataMind OS restarts a failed run by itself, when a step failed with a temporary database error. Enter 0 to 10. See Monitor and fix a run. | 0 |
| Unit | How the schedule repeats: Minute, Hour, Day or Month. | Minute |
| Frequency | The gap between runs, from 1 to 100. | 1 |
| Schedule Day | The day of the month for a Month schedule, from 1 to 31. Used only with Month. | 1 |
| Start Time | The first time the schedule may start a run. | 00:00 |
| End Time | The last time the schedule may start a run. Shown only for Minute and Hour, and it must be after Start Time. | 23:59 |
| Timezone | The time zone that Start Time, End Time and Schedule Day are read in. Editing the workflow keeps it unless you choose another. | Your browser's time zone |
| Schedule Status | On lets the schedule start runs. Off stops it, the same as Off on the card. | On |
| Ignore Error | When on, the schedule keeps starting runs after a failed or aborted run. | Off |
For how these fields decide when a run starts, see Schedules and when a workflow starts.
For an ANY API data source, a hint under Batch Size shows the cap on how many ANY API tables may load at once across all workflows. When your number is higher than the cap, the hint adds that only the capped number of these run in parallel. An administrator sets the cap under Admin > System Configuration > Health; see Scheduler, health, maps and connector safety.
Your permissions depend on the type of workflow.
| To | You need |
|---|---|
| Add a workflow | Add Lake Workflows, Add Warehouse Workflows or Add WriteBack Workflows |
| Edit a workflow, or switch its schedule on or off | Modify Lake Workflows, Modify Warehouse Workflows or Modify WriteBack Workflows |
| Delete a workflow | Remove Lake Workflows, Remove Warehouse Workflows or Remove WriteBack Workflows |
Without an add permission, the + button is hidden, and Datasource lists only what you may add. Without a modify permission, the card shows View instead of Edit: the dialog opens read-only with locked fields, and it has no buttons at the bottom. For the full picture, see Workflow permissions.
The name contains standard, snapshot or replication, in any capitalisation, even inside another word such as my-replication. Remove the word. When you edit a workflow, keeping its existing name is allowed.
Saving fails. DataMind OS accepts 1 to 100, so enter 100 or less. The field goes higher than that, but the save does not accept more than 100. See Troubleshooting workflows.
It sets how many nodes of one run work at the same time. Higher values let large workflows finish sooner, but they put more load on the source and the database. Nodes above the number wait and start as others finish.
The data source and the workflow type are fixed once the workflow exists. To load from another data source, create a new workflow.
The switch appears only when you create a workflow, you can add Warehouse workflows, and the Warehouse is set up. It never appears when you edit a workflow.
The workflow still holds tables or transformations. Move them to another workflow, then delete again. The message gives the count, and the Delete a workflow steps on this page list where to move each kind.
No. DataMind OS creates these workflows for each source and Writeback destination, and it refuses to delete them.
The button turns on only after you change a field. When editing, if the dialog is locked entirely and shows no buttons at the bottom, you lack the modify permission for this workflow type.
They are two labels on the same dialog: Add a Workflow in the header at the top, and Register Workflow on the main panel below it. When you edit a workflow, both read Edit Workflow.
Yes. Edit the workflow and change Workflow Name. The rules stay the same: at least 2 characters, no standard, snapshot or replication, and not a name another workflow already uses. The reserved-word check is skipped only while the name stays exactly as it is.