This topic describes how to edit, run, and unpublish a task flow, and how to view the publishing records of the task flow.
Edit a task flow
Only the owner of a task flow can edit the task flow.
Go to the editing page of a task flow and click Go to O&M in the upper-right corner.
On the Task Flow Information page, click Edit.
In the lower part of the editing page, click a tab and modify the settings as needed.
On the Task Flow Information tab, you can configure the properties of the task flow, such as the name, owner, stakeholders, and scheduling settings of the task flow. For more information, see Getting started, Configure timed scheduling, and Configure event scheduling.
On the Variable Configuration tab, configure time variables and constants for the task flow. For more information, see Variables.
NoteThe time variables and constants for a task flow can be used in all nodes of the task flow. The variables and constants are referenced in the format of
${name}in SQL statements.On the Notification Configurations tab, configure the success and failure notifications for the task flow and timeout notifications and alert notifications for task nodes or the task flow.
On the Operations tab, view the time, operator, and content of the operations on the task flow.
On the Execution Logs tab, view the execution logs of the task node.
Run a task flow
In the upper part of the editing page, select a mode to run the task flow based on your needs.
Modes
Try Run
Run the task flow now.
Dry Run
Task Flow A depends on Task Flow B by using a task node for checking task flow dependencies, but can be run without running Task Flow B. In this case, you can dry run Task Flow B to generate a scheduled trigger record. Then, Task Flow A can be normally run.
Run at a Specific Point in Time
To use this mode, you must define a time variable for a task flow and reference it in SQL statements. The value of the time variable is calculated based on the day before the task flow is run and the specified offset. This allows you to run a task flow at a specific point in time without modifying the SQL statements and related configurations.
Run at a Specific Time Range
To use this mode, you must define multiple time variables for a task flow. Only 50 node instances can be run after a task flow is started in this mode.
For example, if the scheduling cycle of a task flow is one day, the task flow instance can run only for 50 days.
NoteTasks in a task flow that runs within a time range are serially run. The tasks must be successfully run at the previous business time before they can be run at the next business time.
Publish or unpublish a task flow
For more information, see Publish or unpublish a task flow.
View the differences between task flow versions
When you modify a task flow that has been published and click Publish to publish the modified task flow, you can click Display differences in the Publish dialog box to view the differences between the latest published version and current editing version of the task flow.
On the comparison page, a red dot signals modifications.
Check whether a task flow is modified
In the upper part of the editing page of a task flow, move the pointer over Publish. If the note block that appears contains the The task flow is modified. You must republish the task flow to make the modification take effect. message, the task flow is modified.
View the publishing records of a task flow
You can view the publishing records of a task flow on the Published Tasks tab of its Task Flow Information page.
You can also perform the following operations on the task flow of a specific version:
DAG: view the directed acyclic graph (DAG) of the task flow of the specified version.
Backfill Data: generates one or more task flow instances for a specific point in time or specific time range based on the specified version.
Rollback: restores all information about the task flow to the specified version, including task nodes and configurations.
NoteAfter you roll back a task flow, you must republish the task flow for the rollback to take effect.
Export: exports the configuration file of the edges and task nodes of the specified version.
If a task flow has multiple published versions, you can select two versions and click Version Comparison to view the differences between the two versions.