Type | Scenario | Detailed Documentation |
Notebook task | Reference a Studio Notebook file to run Python + Spark code. | |
Python File task | Reference a Studio Python file to run single-file Python code. | |
Ray task | Submit a Ray job (zip package) to a Ray cluster. | |
SQL task | Reference a Studio SQL file to run Spark SQL. | |
Offline data ingestion task | Reference an offline synchronization task in the data ingestion module. | |
IF ELSE conditional task | Control downstream execution paths based on conditional branches. | |
For Each loop task | Execute internal tasks in a loop based on the dataset. | |
Nested workflow task | Call another workflow in the current workflow. | |
Quality monitoring task | Reference a data quality task to run rule checks. |
Item | Rule |
Character Set | Chinese and English characters, digits, underscores _, and hyphens - |
Length | 1–512 characters |
Unique | Task names must be unique within the same workflow. |
Validation | Spaces are automatically converted to underscores. If the input contains invalid characters or a duplicate name, a red message is displayed below the input box. |
Field | Description | Required |
Upstream dependent tasks | Multi-select dropdown. Options are other tasks in the current workflow. When a task is created, the task currently selected on the canvas is automatically selected. | No (displayed only in multi-task scenarios) |
Run Condition (Trigger Rule) | Single choice / advanced mode | Yes |
Option | Trigger Condition | Downstream Status When Upstream Is Not Met |
All Successful (Default) | All upstream tasks succeed | Upstream Failed / Excluded |
All Failed | All upstream tasks fail or upstream failed | Excluded from Running |
All Finished | All upstream tasks reach a final state (Succeeded / Failed / Upstream Failed / Excluded). | Waiting for Upstream |
All Finished and at Least One Succeeded | All upstream tasks completed + at least one succeeded. | Excluded from Running |
All Finished and at Least One Failed | All upstream tasks completed + at least one failed. | Excluded from Running |
All Excluded from Running | All upstream tasks are excluded from running. | Excluded from Running |
All Finished and None Failed | All upstream tasks completed and none failed. | Upstream Failed |
No Failure and at Least One Success | No failures and at least one success | Excluded from Running |
None Excluded from Running | All upstream tasks have actually run (Succeeded / Failed / Upstream Failed). | Excluded from Running |
At Least One Failure | Trigger immediately when any upstream task fails. | Wait for upstream until failure; if all complete without failure, exclude from running. |
At Least One Success | Trigger immediately when any upstream task succeeds. | Wait for upstream until success; if all complete without success, exclude from running. |
At Least One Finished | Trigger immediately when any upstream task reaches a final state. | Waiting for Upstream |
{upstream task} = {state set} expressions and use any one / all to determine the trigger condition. For example:task_A = success, failure AND task_B = success
success / failure / upstream failure / excluded from run.AND / OR from the drop-down list. The default is OR.Status | Description | Final State |
Excluded from Running (Excluded) | Excluded because the task run conditions are not met, or the upstream node is a branch node and this node is not on the branch-selected path. | Yes |
Skipped | The entire workflow is skipped due to concurrency limit. | Yes |
ExecutionConditionsNotMet. The run details page displays a message such as "The current task run condition is ${specific run condition}, which is not met, so the task is excluded from running."Source | Action |
Workflow-delivered parameter | Workflow parameters are automatically delivered to tasks. Parameter names are grayed out and parameter values cannot be modified. You need to modify them in the workflow parameters. |
Task parameter. | Add a parameter to the task. When the parameter has the same name as a workflow parameter, the task parameter has a higher priority (task parameter > workflow parameter). |
Item | Rule |
Parameter Name | All languages, uppercase and lowercase letters, digits, _, and -, up to 128 characters |
Parameter Value | String, up to 2048 characters |
Metric Value | Purpose | Default Value |
Running Time | Duration of task running | 00h00m00s (not in effect) |
Waiting duration | Duration of waiting for upstream or resources | 00h00m00s (not in effect) |
Completion time. | Completion time (periodic runs only) | Empty (not in effect) |
Parameter | Description | Default Value |
Retry after Execution Failure | Whether to automatically retry upon failure. | Selected |
Behavior after Timeout | Mark as Failed Directly / Trigger Retry | Mark as Failed Directly |
Maximum Number of Retries | 1–999 | 4 Times (5 Executions in Total) |
Retry Interval | Value + unit (seconds/minutes/hours), with a maximum unit value of 9999. | 5 Minutes |
Operation | Description |
Creating a Task | Button text for creating a task. |
Save Task | Button text for editing an existing task. |
Leave Without Saving | Dialog prompt: Cancel / Discard changes / Save and continue. |
Resource Type | Description |
Computing Resource | Selected independently by each task type; typically a Spark / Ray resource group. For details, see Compute Resource Overview. |
フィードバック