Task Operation and Maintenance
Last updated:2025-09-09 15:04:35
When users complete computing task configuration and task node orchestration in Offline Development > Orchestration Space and submit for scheduling, they can manage data workflows and computing tasks in the task ops interface, including operations such as starting up, suspending, decommissioning, and deleting workflow executions, as well as starting up, suspending, decommissioning, and deleting computing tasks. Other features include viewing workflow details, task execution history, upstream and downstream relationships between tasks, and task execution instances.
Prerequisites
Workflows and tasks can be viewed and operated in task ops after submission. To configure workflows or tasks and submit for scheduling, refer to Task Development.
Use Limits
For data sync tasks created in the Data Integration module, go to Data Integration - Instance Ops for maintenance. Refer to Real-time Synchronization Task Configuration and Ops or Offline Synchronization Task Configuration and Ops for related content.
Operation Steps
Access the Task Ops
1. log in to WeData console.
2. Click Project List on the left menu and find the target project requiring maintenance operations.
3. After selecting a project, click to enter the Ops center module.
4. Click Task Ops on the left menu.
Workflow Operations
Workflow List
Select the Workflow List tab on the Task Ops page. The Workflow List page displays data workflows that have been published and entered the maintenance phase. You can view the current status and schedule cycle of workflows in the list, and perform various maintenance operations to ensure efficient, smooth, and reliable data processing flows.
Workflow list info:
Feature description:
Information | Description |
workflow name | Display the workflow name and ID. Click the   Submission time: Displays the first submission and last submission for operations of the current workflow in the format: yyyy-MM-dd HH:mm:ss. Task info: Displays the number of compute task nodes involved in the current workflow orchestration. Type distribution: Use a ring chart to show the proportion of compute task nodes by type in the workflow. Period distribution: Use a ring chart to show the proportion of different scheduling policies for compute task nodes by type in the workflow. Run history: Shows the workflow run history (only displayed when all tasks under the workflow are in the same period). DAG diagram: Displays the schematic diagram of the current workflow's DAG compute node orchestration. You can view the task type and node orchestration logic of each compute task node. Hover the cursor over a task node to view its task ID, project name, workflow name, responsible person, task type, task status, task cycle, and scheduling plan. The DAG diagram provides features like zoom in, zoom out, 1:1, locate task, and filter in the upper right corner for easy canvas operation. The filter function supports selecting four statuses: scheduling in progress, paused, offline, and invalid. Once selected, tasks in the status will be displayed on the canvas. |
folder | Displays the parent folder directory of the workflow in the orchestration space, facilitating the identification and unified management of workflow ownership. |
Owner | Displays the owner of the workflow, clarifying the maintenance responsibility of the workflow, defaulting to the creator of the workflow. |
Tasks | Displays the number of compute task nodes involved in workflow orchestration. |
Status | The running state of the workflow allows users to judge whether the workflow executes as expected based on its status. In total, there are 6 states: All scheduling, All Paused, all offline, partially scheduling, all unscheduled, all expired. All scheduling in progress: All tasks under the workflow are in "scheduling in progress" All Paused: All tasks under the workflow are in "paused" All offline: All tasks under the workflow are in "Offline" Partially scheduling: Some tasks under the workflow are in "scheduling in progress", while others are in "paused" or "Offline" statuses. All unscheduled: All tasks under the workflow are in non-scheduling status, including "Offline", "paused", and "invalid". All expired: All tasks under the workflow are in "invalid" and cannot start or suspend. |
Workflow Operations
Feature description:
Operation | Description |
Start | Select in front of the workflow name and use the feature button at the top to batch start, suspend, or decommission the selected workflow execution. Start: only applicable to tasks with status "paused". After starting the workflow, all tasks in the workflow will be in a normally running state and generate instances according to the scheduling cycle. Suspend: only applicable to tasks with status "scheduling in progress". After suspending the workflow, the tasks in the workflow will not generate new instances. Decommission: only applicable to tasks with status "scheduling in progress", "paused", or "invalid". Once offline, the task status will be set to "Offline", and no instances will be generated. To re-execute, resubmit in the orchestration space.  |
| Pause |
| Abolish |
Start All | For workflows in the "All Paused", "partially scheduling", or "all unscheduled" running state, you can start all nodes belonging to the "paused" status. |
Take All Offline | For workflows in the "All scheduling", "All Paused", "partially scheduling", "all unscheduled", or "all expired" running state, you can take all nodes belonging to the "scheduling in progress", "paused", or "invalid" status offline. Once offline, the task status will be set to "Offline", and no instances will be generated. To re-execute, resubmit in the orchestration space. |
All paused | For workflows in the "All scheduling" or "partially scheduling" running state, you can suspend all nodes belonging to the "scheduling in progress" status. After suspending the task, it will not generate new instances. The suspended task can return to the scheduling state by launching the operation. |
Data Replenishment | Perform supplementary execution for failed instances and historical missing instances in computing task scheduling, supplementing missing or failed data processing task cycles. For more information, see Data Replenishment. |
Modify Owner | The workflow owner defaults to the workflow creator. Modifications are allowed to assign other users under the account as responsible persons, supporting specifying multiple users as owners. |
Delete Workflow | To delete a workflow in operations, ensure all computing tasks in the workflow are offline and the workflow execution status is "all offline". The workflow can then be deleted. Workflows removed from operations will not be deleted from the orchestration space. Subsequently, you can submit the deleted workflow for operations again in the orchestration space. |
Workflow development | Navigate to the corresponding workflow canvas in the orchestration space, a quick access channel for workflow operations and workflow editing. |
If strict task operation mode is enabled, suspend, decommission, and delete operations in the workflow only take effect on tasks without downstream dependencies that are not in the "Offline" state. The following table describes the results of suspend, decommission, and delete operations after enabling strict mode.
Note：
Note: Toggle strict task operation mode on or off in Project Management > Basic Information Configuration > Data Development Configuration.
Operation | Description |
Pause workflow | Suspending a workflow only takes effect on tasks without downstream dependencies that are not in the "Offline" state. In the pop-up dialog box, you can view tasks that allow operations, including task name, task type, scheduling type, responsible person, and associated workflow.  |
Decommission workflow | Decommissioning a workflow only takes effect on tasks without downstream dependencies that are not in the "Offline" state. In the pop-up dialog box, you can view tasks that allow operations, including task name, task type, scheduling type, responsible person, and associated workflow.  |
Delete Workflow | If the workflow to be deleted has downstream tasks from other workflows, a popup window will prompt that the workflow cannot be deleted.  Click to view existing dependency details, you can view specific dependent workflows and tasks.  |
Workflow filtering and list refresh:
Operation | Description |
Filter by Workflow Name/ID | Filter by string contained in Workflow Name or ID. For multiple Workflow Names/IDs, please use "|" to separate. |
Filter by Owner | Filter by Owner. After clicking the form, you can manually input or make multiple selections in the drop-down list. |
Filter by folder | Filter workflows in the orchestration space by their folder directory. You can unfold multi-level directories and support multiple selections.  |
Workflow refresh | Click on the right  |
Task Ops
Task Ops List
Select the Task List tab on the Task Ops page. The Task List page displays compute task nodes in published workflows. You can view the current scheduling status and cycle of tasks in the list, and perform a series of feature operations to maintain compute tasks, ensuring stable, valid, and reliable data processing nodes.
Task list information:
Feature description:
Information | Description |
Task name/ID | Copying the task name and ID is supported. Click the task name to navigate to the task details page > task lineage. |
Owner | Displays the owner of the computing task, clarifying the maintenance responsibility of the computing task, defaulting to the creator of the computing task. |
Status | The running state of the computing task allows users to judge whether the task executes as expected based on its status. In total, there are 5 states: Scheduling in progress, Paused, Offline, Invalid. Scheduling in progress: The computing task is in the normal "scheduling in progress" state and will generate task instances as per the scheduling plan. Paused: The computing task is in the "paused" state and will not generate new instances, while existing instances continue to run. Offline: The computing task is in the "Offline" state. No new instances are generated for offline tasks. To reschedule, resubmit in the orchestration space. Invalid: The task is in the "invalid" state, meaning the current time has exceeded the effective time of the task configuration. Invalid tasks cannot be started or paused. |
folder | Displays the folder directory of the computing task in the orchestration space, facilitating the identification of task ownership and unified management. |
Workflow Directory | Displays the workflow name of the computing task in the orchestration space, facilitating the identification of task ownership and unified management. Click the workflow name to navigate to the corresponding task's workflow configuration page. |
Task type | Task type of the computing task. |
Scheduling type | Scheduling period of the computing task. |
Execution Resource Group | Execution resource group for task configuration. |
Last Submission Time | Display the last submission for operations after the computing task was updated, in the format: yyyy-MM-dd HH:mm:ss. |
First execution time | Display the first Generation Instance Execution time for the computing task in the scheduling cycle, in the format: yyyy-MM-dd HH:mm:ss. |
Creation time. | Display the first submission for operations of the computing task, in the format: yyyy-MM-dd HH:mm:ss. |
Task operations:
Feature description:
Operation | Description |
Start | Batch operations and single task operations. For batch operations, check the task name and use the feature button at the top. For single task operations, click the operation item in the Operation column of the task list. Start: only applicable to tasks with status "paused". After starting the task, it will be in a normal scheduling status and generate instances according to the scheduling cycle. |
Pause | Suspend: only applicable to tasks with status "scheduling in progress". After pausing the task, it will not generate new instances. You can choose whether to terminate generated instances during the pause operation. |
Abolish | Decommission: only applicable to tasks with status "scheduling in progress", "paused", or "invalid". Once offline, the task status will be set to "Offline", and no instances will be generated. To re-execute, resubmit in the orchestration space. |
Data Replenishment | Data Replenishment: Perform supplementary execution for failed instances and historical missing instances in task scheduling, supplementing missing or failed data processing task cycles. For details, see Data Replenishment. |
Setting Alarms | Alarm Setting: Configure alarm monitoring for task running status, so that O&M personnel can quickly detect task execution exceptions and respond promptly. For details, see Task Alarm. |
Modify Owner | Modify Owner: Target a task to modify its responsible person and clarify operation and maintenance responsibility attribution for computing tasks. The same task can add multiple responsible persons at once. |
Delete | Delete: Only support deletion of computing tasks with the status "Offline". You can send notification of task deletion messages to the task owner. If multiple computing tasks are selected, other tasks in running status will not be deleted by default. There are two deletion methods. After deletion, downstream tasks run normally. After deletion, downstream tasks all fail to run. |
View Instance | Navigate to the List Interface of the corresponding computing task's generated instance, where you can view the instance running status, running time, etc., and perform feature operations on the instance. |
View Details | Redirect to the task details page, support basic task operations, and view task basic information. For an introduction to the task details page, see below. |
Task Development | Navigate to the corresponding compute node configuration interface in the orchestration space. This is a quick access channel for task operations to edit compute task nodes. For details, see Task Development. |
Task filter:
Operation | Description |
Filter by Task Name/ID | Supports fuzzy matching by task name or task ID. |
Filter by folder | Filter tasks in the orchestration space by their folder name. You can unfold multi-level directories and support multiple selections. |
Filter by Workflow Directory | Filter by workflow name of the computing task. |
Filter by task type/data source | Support filtering by task type. If you select offline synchronization task, you can filter by source data table and target data table. |
Quick actions:
Operation | Description |
Workflow refresh | Click the  |
Download | Click the  |
Display column adjustment | Click the  |
Task Details Page
The Task Details Page is a collection of task information and operations, including basic information about the task, basic operations, execution situation of historical instances, task lineage, etc. Task ops can be performed on this page.
The task details page contains three tabs: Execution History, Execution Curve, and Task Lineage.
Content | Description |
Execution History | Show the basic information of the task history instance. Filter: support by instance data time, start time to filter instances. Statistics: count the total number of instances in the filter range, including instances in various statuses (waiting for upstream, wait for event, awaiting execution, running, success, failure). Instance list: show basic info and perform operations.  |
execution curve | Show the execution time curve of task history instances. Change trend of execution duration: Viewable for the last 25, 50, or 100 instances. Users can learn about change details of historical instance execution duration to determine whether there are exceptions. Start/end time trends: Viewable for the last 25, 50, or 100 instances to track execution start time and end time trends.  |
task lineage | Display the lineage information of the current task. DAG mode and list mode are divided. List mode is recommended for complex lineage relationships with many nodes. The DAG in task lineage shows the upstream and downstream tasks of the current node, with filtering by status. Selectable statuses include scheduling in progress, paused, offline, and invalid.  |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback