How to view and manage one-time tasks - Dataphin - Alibaba Cloud Documentation Center

One-time tasks are tasks that have been submitted to the Operation Center and have a scheduling type of manual node. One-time tasks do not run automatically. Instances are generated only when the tasks are manually triggered to run. This topic describes the operations and maintenance features for one-time tasks.

Access the one-time task page

In the top navigation bar of the Dataphin homepage, choose Development > Task Operations.
In the left-side navigation pane, choose Task Operations > One-Time Task to open the One-Time Task page.
In the top navigation bar, select the production or development environment.

Introduction to the one-time task page

The one-time task page consists of the filtering and search area, filtering area, one-time task list, and batch operations area. You can perform operations and maintenance operations on submitted one-time tasks on the one-time task page.

Section	Description
①Filtering and search area	Allows you to filter one-time tasks by entering the task object name or ID, which is useful for quickly filtering the required one-time tasks when you know the task object name or ID. You can also select My Tasks or Updated Today for filtering. My Tasks: One-time tasks for which the current account is the owner. Updated Today: One-time tasks that are updated on the current day. Filter: Click Filter to expand the filtering area. The filtering options include the following: Task Type: Filter by the manual task types created in Dataphin. The supported task types vary depending on the environment. Refer to the actual page display for details. Operation Owner: Filter by the operations and maintenance owner of the task. Priority: Filter by the priority of task execution. You can select multiple priorities, including Highest, High, Medium, Low, and Lowest. Update Time: You can select Today or Custom Time Range for filtering. Project: Filter by the project to which the task belongs. You can select multiple projects for which the current logged-in user has the Operations - Access Directory permission. Resource Group: Filter by the schedule resource group configured for the one-time task. You can select multiple resource groups. If you need to reselect, click Reset to quickly clear all selected filter conditions.
②One-time task list area	The one-time task page displays the one-time tasks that have been submitted to the Operation Center in a list format. The list shows the current Task Object, Priority, Operation Owner, Project, HTTP path, Resource Group, Last Update Time, and supported Actions. Project: The project to which the task belongs, displayed in the format `Project English name (Project Chinese name)`. HTTP path: Displays the production environment HTTP path or development environment HTTP path for DATABRICKS_SQL type tasks, depending on the selected production or development environment. Note Only DATABRICKS_SQL type tasks support displaying this item. Other task types display -. Resource Group: The name of the schedule resource group used when the task instance runs. If the custom resource group specified for the task is not in an active state, it will be automatically replaced with the project default resource group. If the project default resource group is not in an active state, it will be automatically replaced with the tenant default resource group. The priority is Custom resource group > Project default resource group > Tenant default resource group. Note When changing the project default resource group, there may be a delay in the display update here. However, the actual execution will use the modified resource group. Tenant default resource group: Does not belong to any project. A tenant has only one default resource group. When a task does not specify a separate custom resource group or the project does not specify a project default resource group, the tenant default resource group is used for scheduling, only for exclusive resource tasks (except SQL tasks, Virtual tasks, etc.). Actions: The Actions column in the list displays the operations and maintenance management operations supported for one-time tasks. For more information, see Operations supported in the one-time task list.
③Batch operations area	You can use the operations and maintenance functions provided in the batch operations area to process one-time tasks in batches, improving operational efficiency. For operation details, see Batch operations for one-time tasks.

Operations supported in the one-time task list

Operation	Description
View Node Code	You can enter the code details page to view the node code of the one-time task.
View Instances	View the one-time instances generated by the task execution. You can also perform operations and maintenance management on the one-time instances.
Run	Manually trigger the task to run. For more information, see Run a one-time task.
Edit Development Node	Enter the editing page of the task in the Dev project to edit the task. This is only applicable to the Dev-Prod development mode. Note After editing the development node, you need to submit or publish it for the production node data to be updated.
Edit Node	Edit the node of a task. This is only applicable to the Basic mode. Note After editing the node, you need to submit or publish it for the production node data to be updated.
View Node Script	View the associated dependency graph of the pipeline task. Note Only one-time tasks submitted from the Data Integration module support viewing node scripts.
View Production Node	Enter the Prod project to view the task node data.
Modify Operation Owner	Modify the operations and maintenance owner of the task. Note This is only applicable to tasks in Prod and Basic projects (i.e., production environment tasks). You can only select members within the tenant.
Configure Monitoring And Alerting	Configure monitoring rules for task execution. During task execution, if a monitoring rule is triggered, the system will send you an alert message, allowing you to detect anomalies promptly and ensure normal production of business data. For specific operations, see Overview of offline task monitoring. Note The system only supports configuring monitoring for tasks in Prod and Basic projects (i.e., production environment tasks).
Modify HTTP Path	Modify the production environment HTTP path for the corresponding task. You can select from all HTTP paths configured for the production project's corresponding cluster. Note This operation is only supported when selecting DATABRICKS_SQL tasks in the production environment.
Modify Schedule Resource Group	You can modify the schedule resource group used when the task instance runs. Note Only tasks in Prod and Basic projects can have their schedule resource group modified. The modification does not affect already generated instances and only affects newly generated instances. If you need to modify the resource group used by already generated instances, you can do so in the instance list.

View node code details

Click the Actions trta icon in the column or click the task object name to display the details of the current task on the right side of the page. You can click the icon to hide the one-time task list on the left and enlarge the one-time task details page.

Section	Description
①Operations and maintenance management area	Provides entry points for operations and maintenance management of one-time tasks. View Operation Log: View the operation log of the current task, which includes the operation time, operator, and specific operation. View One-Time Instances: Enter the one-time instance page to view the one-time instances generated by the current task execution. Note Only one-time tasks that have been run will generate one-time instances. View Node Code: View the node code of the pipeline task. Note Only pipeline tasks support viewing node code. After viewing the node code, click View Node Script to return to the page that visually displays the upstream and downstream components of the pipeline task. Edit Development Node: Enter the editing page of the current task in the Dev project to edit the task. Note Only the Dev-Prod development mode supports this operation. Edit Node: Enter the editing page of the current task to edit the task. Note Only the Basic mode supports this operation. View Production Node: Enter the Prod project to view the current task configuration. Refresh: Refresh the current one-time task. Run: Click Run, and in the Run dialog box, configure the data timestamp, number of concurrent running groups, running order, and parameter configuration. For detailed configuration instructions, see Run a one-time task.
②Node information area	Displays the node information and running information of the one-time task.
③Task code area	One-time tasks submitted from the Data Development module support viewing task calculation results. One-time tasks submitted from the Data Integration module display the upstream and downstream components of the pipeline task by default. You can also click View Node Code at the top of the page to view the node script of the pipeline task.

Run a one-time task

Click Run to open the Run dialog box.

In the Run dialog box, configure the following parameters.

Parameter	Description
Data Timestamp	You can select By Range, By Cycle, or Custom. By Range is selected by default, with the default range value of `current data timestamp ~ current data timestamp`. By Range: After selecting By Range, you need to select the time range for the interval. The time range span cannot exceed 1 year. This is suitable for scenarios where the current task needs to run continuously for multiple data timestamps. By Cycle: After selecting By Cycle, you need to select the time range for the cycle and specify the dates for each month or each week. The time range span cannot exceed 1 year, with the default being `current data timestamp ~ current data timestamp`. This is suitable for scenarios where the current task needs to run on specific days of the week or specific dates of the month within multiple consecutive data timestamps. Weekly: Run on the selected days of the week each week, such as every Monday and Tuesday. Monthly: Run on the selected dates each month, such as the 1st, 5th, and 10th of each month. Note Month end refers to the last day of each month. Custom: Supports entering multiple data timestamps in the format `YYYY-MM-DD`, with multiple data timestamps separated by line breaks. The range of data timestamps that can be entered is `1900-01-01 ~ present`. Dates outside this range will not take effect.
Concurrent Running Number	The default is 1. You can enter an integer between 1 and 12.
Running Order	You can select Data Timestamp Ascending or Data Timestamp Descending. The default is Data Timestamp Ascending, which means execution proceeds in ascending order of data timestamps.
Parameter Checking	If the current one-time task includes local variables, the one-time task will run according to the configured parameter values after the local parameter configuration is complete. You can select Fill Empty Values. Additionally, the parameter values will remain consistent across all instances generated by the current task.

After completing the configuration, click Submit.

Batch operations for one-time tasks

Operation	Description
Run	After selecting multiple tasks, click Run at the bottom of the list to configure the data timestamp, number of concurrent running groups, and running order for batch execution. For parameter descriptions, see Run a one-time task. Note If you select only a single one-time task, you can also configure parameters. You can select up to 100 one-time tasks for a single batch operation.
Modify Operation Owner	After selecting multiple tasks, click Modify Operation Owner at the bottom of the list to modify the operations and maintenance owner for multiple tasks simultaneously. Note You can only select members within the current project. This is only applicable to Prod and Basic projects.
Modify Priority	After selecting multiple tasks, click Modify Priority at the bottom of the list to modify the priority of multiple tasks simultaneously. At the same time, among all tasks that meet the scheduling conditions, tasks with higher priority will run first. After modifying the task priority, the next scheduling will be based on the latest priority. The task priority modification takes effect immediately, without the need to submit or publish the task. Note This is only applicable to Prod and Basic projects (i.e., production environment tasks).
Modify HTTP Path	You can modify the production environment HTTP path for multiple DATABRICKS_SQL tasks. If the selected DATABRICKS_SQL tasks belong to different Databricks clusters, you can specify HTTP paths for different clusters separately. You can select from all HTTP paths configured for the corresponding cluster. Note This operation is only supported when selecting DATABRICKS_SQL tasks in the production environment.
Modify Schedule Resource Group	After selecting multiple tasks, click Modify Schedule Resource Group at the bottom of the list to batch modify the schedule resource group used when the instances generated by multiple tasks run. Note When selecting tasks from multiple projects, the target schedule resource group only lists the schedule resource groups that are commonly authorized for all these projects. It is recommended to filter for a single project first, and then perform batch settings. The modification does not affect already generated instances and only affects newly generated instances. If you need to modify the resource group used by already generated instances, you can do so in the instance list.