diff --git a/docs/docs/en/guide/task/dependent.md b/docs/docs/en/guide/task/dependent.md index 3a97bb50d7..b8e63d03e9 100644 --- a/docs/docs/en/guide/task/dependent.md +++ b/docs/docs/en/guide/task/dependent.md @@ -7,20 +7,24 @@ Dependent nodes are **dependency check nodes**. For example, process A depends o ## Create Task -- Click `Project -> Management-Project -> Name-Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page. +- Click `Project Management -> Project Name -> Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page. - Drag from the toolbar task node to canvas. ## Task Parameter -- **Node name**: The node name in a workflow definition is unique. -- **Run flag**: Identifies whether this node schedules normally, if it does not need to execute, select the `prohibition execution`. -- **Descriptive information**: Describe the function of the node. -- **Task priority**: When the number of worker threads is insufficient, execute in the order of priority from high to low, and tasks with the same priority will execute in a first-in first-out order. -- **Worker grouping**: Assign tasks to the machines of the worker group to execute. If `Default` is selected, randomly select a worker machine for execution. -- **Environment Name**: Configure the environment name in which run the script. -- **Times of failed retry attempts**: The number of times the task failed to resubmit. -- **Failed retry interval**: The time interval (unit minute) for resubmitting the task after a failed task. -- **Delayed execution time**: The time (unit minute) that a task delays in execution. +| **Parameter** | **Description** | +| ----- | -----------| +| Node name | Unique name of node in workflow definition. | +| Run flag | Identifies whether this node schedules normally. | +| Description | Describe the function of the node. | +| Task priority | When the number of worker threads is insufficient, execute in the order of priority from high to low, and tasks with the same priority will execute in a first-in first-out order. | +| Worker group | Assign tasks to the machines of the worker group to execute. If `Default` is selected, randomly select a worker machine for execution. | +| Task group name | The group in Resources, if not configured, it will not be used. | +| Environment Name | Configure the environment name in which run the script. | +| Number of failed retries | The number of times the task failed to resubmit. | +| Failed retry interval | The time interval (unit minute) for resubmitting the task after a failed task. | +| Delayed execution time | The time (unit minute) that a task delays in execution. | +| Pre task | Selecting a predecessor task for the current task, will set the selected predecessor task as upstream of the current task. | ## Examples diff --git a/docs/docs/en/guide/task/sub-process.md b/docs/docs/en/guide/task/sub-process.md index 8b84db8fe7..adcd9e3fda 100644 --- a/docs/docs/en/guide/task/sub-process.md +++ b/docs/docs/en/guide/task/sub-process.md @@ -6,20 +6,23 @@ The sub-process node is to execute an external workflow definition as a task nod ## Create Task -- Click `Project -> Management-Project -> Name-Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page. +- Click `Project Management-> Project Name -> Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page. - Drag from the toolbar task node to canvas to create a new SubProcess task. ## Task Parameter -- Node name: The node name in a workflow definition is unique. -- Run flag: Identifies whether this node schedules normally. -- Descriptive information: Describe the function of the node. -- Task priority: When the number of worker threads is insufficient, execute in the order of priority from high to low, and tasks with the same priority will execute in a first-in first-out order. -- Worker grouping: Assign tasks to the machines of the worker group to execute. If `Default` is selected, randomly select a worker machine for execution. -- Environment Name: Configure the environment name in which run the script. -- Timeout alarm: Check the timeout alarm and timeout failure. When the task runs exceed the "timeout", an alarm email will send and the task execution will fail. -- Sub-node: It is the workflow definition of the selected sub-process. Enter the sub-node in the upper right corner to jump to the workflow definition of the selected sub-process. -- Predecessor task: Selecting a predecessor task for the current task, will set the selected predecessor task as upstream of the current task. +| **Parameter** | **Description** | +| ---- |---------| +| Node name | Unique name of node in workflow definition. | +| Run flag | Identifies whether this node schedules normally. | +| Description | Describe the function of the node. | +| Task priority | When the number of worker threads is insufficient, execute in the order of priority from high to low, and tasks with the same priority will execute in a first-in first-out order. | +| Worker group | Assign tasks to the machines of the worker group to execute. If `Default` is selected, randomly select a worker machine for execution. | +| Task group name | The group in Resources, if not configured, it will not be used. | +| Environment Name | Configure the environment name in which run the script. | +| Timeout alarm | Check the timeout alarm and timeout failure. When the task runs exceed the "timeout", an alarm email will send and the task execution will fail. | +| Child node | It is the workflow definition of the selected sub-process. Enter the child node in the upper right corner to jump to the workflow definition of the selected sub-process. | +| Pre task | Selecting a predecessor task for the current task, will set the selected predecessor task as upstream of the current task. ## Task Example @@ -41,6 +44,6 @@ After creating the sub_process, create a corresponding shell task for printing " ![subprocess_task03](../../../../img/tasks/demo/subprocess_task03.png) -## Notice +## Note When using `sub_process` to recall a sub-node task, you need to ensure that the defined sub-node is online status, otherwise, the sub_process workflow will not work properly.