All Products
Search

This Product

    Dataphin:Manage one-time tasks

    Document Center

    Dataphin:Manage one-time tasks

    Last Updated:Jan 13, 2026

    One-time tasks are submitted to the Operation Center with the schedule type set to manual. These tasks do not run automatically. Instances are generated only when you manually trigger the tasks. This topic describes the Operations and Maintenance (O&M) features for one-time tasks.

    Go to the one-time task page

    1. In the top menu bar of the Dataphin home page, choose Develop > O&M.

    2. In the navigation pane on the left, choose O&M > One-Time Task to go to the One-Time Task page.

    3. In the top menu bar, select the production or development environment.

    One-time task page overview

    The one-time task page includes a filter and search area, a list operations area, a one-time task list, and a batch operations area. On this page, you can perform O&M operations on submitted one-time tasks.

    image

    Section

    Description

    ① Filter and search area

    Filter one-time tasks by task object name or ID. This is useful for quickly finding a specific task. You can also select My Tasks or Updated Today to filter tasks.

    • My Tasks: One-time tasks for which the current account is the owner.

    • Updated Today: One-time tasks that were updated on the current day.

    • Project: Filter by project. You can select multiple projects for which the current logged-on user has the O&M - Access Directory permission.

    • Filter: Click Filter to expand the filter area. The filter options include the following:

      • Task Type: Filter by the one-time task type created in Dataphin. Supported task types vary by environment. The task types displayed on the page prevail.

      • Operation Owner: Filter by the O&M owner of the task.

      • Priority: Filter by task execution priority. You can select multiple priorities, including Highest, High, Medium, Low, and Lowest.

      • Update Time: Select Today or a custom time range to filter tasks.

      • Resource Group: Filter by the schedule resource group configured for the one-time task. You can select multiple resource groups.

      • Tag: Select one or more tag values to filter tasks.

      To reselect, click Reset to clear all selected filter conditions.

    ② List operations

    • Customize list headers: Click the image icon to select the items to display in the list and adjust their order.

      Note

      • The first column and the Actions column cannot be hidden or reordered.

      • If you clear the browser cache or switch to a different browser, the table header settings are reset to default.

    • Refresh list: Click the image icon to refresh the current list.

    ③ One-time task list

    The one-time task page lists the one-time tasks that are submitted to the Operation Center. The list shows the Task Object, Priority, Operation Owner, Project, HTTP path, Resource Group, Last Update Time, Tag, and supported Actions.

    • Project: The project to which the task belongs. The format is Project English Name (Project Chinese Name).

    • HTTP path: Displays the production or development environment HTTP path for Databricks SQL tasks, based on the selected environment.

      Note

      Only Databricks SQL tasks support this item. For other task types, - is displayed.

    • Resource Group: The name of the schedule resource group that the task instance uses at runtime.

      If the custom resource group specified for the task is not active, the project's default resource group is used instead. If the project's default resource group is not active, the tenant's default resource group is used. The priority is: Custom resource group > Project default resource group > Tenant default resource group.

      Note

      When you change the project's default resource group, the display here may be delayed. However, the task runs using the modified resource group.

      Tenant default resource group: This resource group does not belong to any project, and each tenant has only one default resource group. When a task does not specify a custom resource group or a project does not specify a project default resource group, the tenant default resource group is used for scheduling, which applies only to exclusive resource tasks (excluding tasks such as SQL and Virtual tasks).

    • Actions: The Actions column lists the supported O&M operations for one-time tasks. For more information, see Operations in the one-time task list.

    ④ Batch operations area

    Use the batch operations area to perform O&M on multiple one-time tasks at a time. This improves efficiency. For more information, see Batch operations for one-time tasks.

    Supported operations for the one-time task list

    Operation

    Description

    View Node Code

    Go to the code details page to view the node code of the one-time task.

    View Instances

    View the one-time instances generated when the task runs. You can also perform O&M on the one-time instances.

    Run

    Manually trigger the task to run. For more information, see Run a one-time task.

    Edit Development Node

    Go to the task's edit page in the Dev project to edit the task. This applies only to the Dev-Prod development model.

    Note

    After you edit the development node, you must submit or publish it to update the data on the production node.

    Edit Node

    Edit the node of a task. This applies only to the Basic model.

    Note

    After you edit the node, you must submit or publish it to update the data on the production node.

    View Node Script

    View the dependency graph of the pipeline task.

    Note

    Only one-time tasks submitted from the Data Integration module support viewing node scripts.

    View Production Node

    Go to the Prod project to view the task node data.

    Modify Operation Owner

    Modify the O&M owner of the task.

    Note

    • This applies only to tasks in Prod and Basic projects, which are production environment tasks.

    • You can select only members within the tenant.

    Configure Monitoring and Alerting

    Configure monitoring rules for task runs. If a monitoring rule is triggered during a task run, the system sends you an alert message. This helps you promptly detect exceptions and ensure normal data output. For more information, see Overview of offline task monitoring.

    Note

    The system supports monitoring configuration only for tasks in Prod and Basic projects, which are production environment tasks.

    Modify HTTP path

    Modify the production environment HTTP path for the task. You can select from all HTTP paths that are configured for the corresponding cluster in the production project.

    Note

    This operation is supported only when you select Databricks SQL tasks in the production environment.

    Modify Schedule Resource Group

    Modify the schedule resource group that the task instance uses at runtime.

    Note

    • This applies only to tasks in Prod and Basic projects.

    • The modification does not affect existing instances. It affects only new instances. To modify the resource group for an existing instance, go to the instance list.

    View node code details

    In the Actions column, click the trta icon or click the task object name to display the task details on the right side of the page. You can click the image icon to hide the one-time task list on the left and expand the details view.

    image

    Section

    Description

    ① O&M management area

    Provides entry points for O&M of one-time tasks.

    • View Operation Log: View the operation log of the current task. The log includes the operation time, operator, and specific operation.

    • View One-time Instances: Go to the one-time instance page to view the one-time instances generated by the current task run.

      Note

      One-time instances are generated only for tasks that have run.

    • View Node Code: View the node code of the pipeline task.

      Note

      Only pipeline tasks support viewing node code.

      After you view the node code, click View Node Script to return to the page that shows a visualization of the upstream and downstream components of the pipeline task.image

    • Edit Development Node: Go to the edit page of the current task in the Dev project to edit the task.

      Note

      This operation is supported only in the Dev-Prod development model.

    • Edit Node: Go to the edit page of the current task to edit the task.

      Note

      This operation is supported only in the Basic model.

    • View Production Node: Go to the Prod project to view the current task configuration.

    • Refresh: Refresh the current one-time task.

    • Run: Click Run. In the Run dialog box, configure the data timestamp, number of concurrent runs, run order, and parameter settings. For more information, see Run a one-time task.

    ② Node information area

    Displays the node and run information of the one-time task.

    ③ Task code area

    • For one-time tasks submitted from the Data Development module, you can view the task calculation results.

    • For one-time tasks submitted from the Data Integration module, the upstream and downstream components of the pipeline task are displayed 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

    1. Click Run to open the Run dialog box.

    2. In the Run dialog box, configure the following parameters.

      Parameter

      Description

      Data Timestamp

      You can select By Range, By Period, or Custom. By Range is selected by default. The default range is current data timestamp to current data timestamp.

      • By Range: After you select By Range, select a time range. The time range cannot exceed 1 year. This is suitable for scenarios where the current task needs to run continuously for multiple data timestamps.

      • By Period: After you select By Period, select a time range and specify the days of each week or month. The time range cannot exceed 1 year. The default is current data timestamp to current data timestamp. This is suitable for scenarios where the current task needs to run on specific days of the week or month within multiple consecutive data timestamps.

        • Weekly: The task runs on the selected days of each week, such as Monday and Tuesday.

        • Monthly: The task runs on the selected dates of each month, such as the 1st, 5th, and 10th.

          Note

          End of month refers to the last day of each month.

      • Custom: Enter multiple data timestamps in the YYYY-MM-DD format. Separate multiple data timestamps with line breaks. You can enter data timestamps in the range of 1900-01-01 to present. Dates outside this range are invalid.

      Concurrent Runs

      The default value is 1. You can enter an integer from 1 to 12.

      Run Order

      Select Data Timestamp Ascending or Data Timestamp Descending. The default is Data Timestamp Ascending, which means tasks are run one by one in ascending order of data timestamp.

      Parameter Settings

      If the one-time task includes local variables, the task runs with the configured parameter values after the local parameters are configured. You can select Fill Empty Values. The parameter values remain the same for all instances generated by the task.

    3. After you finish the configuration, click Submit.

    Batch operations for one-time tasks

    Operation

    Description

    Run

    Select multiple tasks and click Run at the bottom of the list. Configure the data timestamp, number of concurrent runs, and run order for the batch run. For more information about the parameters, see Run a one-time task.

    Note

    • If you select only a single one-time task, you can also configure parameters.

    • You can select a maximum of 100 one-time tasks for a single batch operation.

    Modify Operation Owner

    Select multiple tasks and click Modify Operation Owner at the bottom of the list to modify the O&M owner for multiple tasks at the same time.

    Note

    • You can select only members within the current project.

    • This applies only to Prod and Basic projects.

    Modify Priority

    Select multiple tasks and click Modify Priority at the bottom of the list to modify the priority for multiple tasks at the same time. At a given time, among all tasks that meet the scheduling conditions, tasks with a higher priority run first. After you modify the task priority, the new priority is used for the next scheduling.

    The priority modification takes effect immediately. You do not need to submit or publish the task.

    Note

    This applies only to Prod and Basic projects, which are production environment tasks.

    Modify HTTP path

    Modify the production environment HTTP path for multiple Databricks SQL tasks. If the selected Databricks SQL tasks belong to different Databricks clusters, specify the HTTP path for each cluster. You can select from all HTTP paths that are configured for the corresponding cluster.

    Note

    This operation is supported only when you select Databricks SQL tasks in the production environment.

    Modify Schedule Resource Group

    Select multiple tasks and click Modify Schedule Resource Group at the bottom of the list to modify in batches the schedule resource group that the instances generated by the tasks use at runtime.

    Note

    • When you select tasks from multiple projects, the target schedule resource group list includes only the resource groups that are authorized for all the selected projects. We recommend that you filter for a single project before you perform batch settings.

    • The modification does not affect existing instances. It affects only new instances. To modify the resource group for an existing instance, go to the instance list.