All Products
Search
Document Center

Dataphin:Manage submitted instances

Last Updated:Jun 23, 2026

Submitted instances are executable instances generated by a backfill data operation on a periodic task or from a pending instance. You can rerun, terminate, pause, resume, or Set to Successful and Continue Scheduling submitted instances.

Access submitted instances

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

  2. In the navigation pane on the left, choose Instance O&M > Backfill Instances.

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

  4. On the Backfill Instances page, click the Submitted Instances tab.

Submitted instances page

The Submitted Instances page lets you monitor and manage generated backfill data instances.

image

Section

Description

Filter and search area

Filter submitted instances by entering an instance object name or ID.

  • Submitted by Me: Filters for instances submitted by the current user.

  • Backfill Failed: Filters for failed backfill instances submitted by the current user.

  • Backfill Unfinished: Filters for backfill instances submitted by the current user that are still running or have not yet finished.

  • Select Project: Filter by the project to which the task belongs. You can select multiple projects for which you have O&M - Access Directory permissions.

    Note

    After you filter by project, the list shows only the instances in the backfill data workflow that belong to the selected projects.

  • Filter: Click Filter to expand filter options. To clear all filters and restore defaults, click Reset. The following filter options are supported:

    • Instance type: Filter by instance type. You can select one or more instance types that your tenant supports.

    • Instance running status: Filter instances by running status. You can select from the following statuses: success, failed, running, not started, waiting for scheduling resources, waiting for scheduling time, and throttling.

    • Backfill status: Filter submitted instances by backfill data status. Backfill statuses include success, failed, not started, and running. For more information, see Backfill data instance status descriptions.

    • Instance owner: Filter submitted instances by owner.

    • Submitter: Filter submitted instances by submitter.

    • Business date: By default, the list shows instances from all dates. You can filter by Today, Yesterday, or a specific date range.

    • Start time: By default, the list shows instances that started running today. You can filter by Today, Yesterday, or a specific day.

    • Submission date: Filter for instances submitted on Today, Yesterday, All, or a specific day.

    • Scheduling resource group: Filter instances by the scheduling resource group used at runtime.

    • Tags: Select one or more task tag values to filter the list.

List operations

  • Switch to tree view: Click the image icon to group instances with the same backfill task name and categorize them by business date. For more information, see View the submitted instance list in tree view.

  • Switch to list view: Click the image icon to display all backfill data instances in a list view.

  • Customize list header: Click the image icon to select which columns to display and to reorder them.

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

    • If you clear your browser cache or switch browsers, the header settings revert to their defaults.

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

Submitted instance list

The Submitted Instances page lists instances generated by periodic tasks. The list includes columns such as Backfill name-business date, Backfill status, Backfill task, Submitter/time, Business date, Runtime, Number of nodes, Tags, and Actions. You can adjust column widths. Your settings are saved in the browser and are lost if you clear your browser history and cookies.

Batch operation area

Process multiple backfill data instances at once. For more information, see Supported batch operations for submitted instances.

Backfill data instance status

The status of a backfill data instance is determined by consolidating the statuses of its individual business date runs as described in the following table.

If a backfill data instance contains paused instances, the Backfill status reflects this. If some instances are paused, the status shows as Partially Paused. If all instances are paused, the status shows as All Paused.

Evaluation order

Consolidated status

Logic

1

Not started

If the instance is initializing or all its constituent instances have a status of not started, the backfill data instance status is not started.

2

Running

If there are instances that are waiting or running and no instances have failed, the backfill data instance status is running.

3

Failed

If any instance has failed, the backfill data instance status is failed.

4

Success

If all instances have a status of success, the backfill data instance status is success.

Submitted instance tree view

The backfill instance list page displays the Backfill name-business date, Backfill status, Backfill task, Submitter/time, Business date, Runtime, Number of nodes, and supported actions.

The tree view for submitted instances has three levels, as shown below.

image

Level

Description

Level 1

Backfill task level: Represents the backfill task. The name is the instance name you configured when you ran the backfill data operation. A new backfill task level is generated each time you submit a backfill data operation.

Level 2

Business date level: Shows all business dates that require data backfilling under the backfill data instance. Each business date corresponds to a folder.

Level 3

Backfill data instance level: Displays the instances generated after performing a backfill data operation on a task. You can also view the instance's dependency DAG. The DAG for backfill data instances is the same for each business date.

  • Level 1 and Level 2: Supported actions for a single backfill data instance.

    Actions

    Description

    View backfill status details

    Click the image icon next to the Level 1 backfill status to view status statistics for all backfill data instances under the current backfill task.

    Terminate all

    Dataphin automatically selects and terminates nodes in the current folder with a status of waiting or running, as well as logical table fields and their dependencies with a status of not started, running, or waiting. Nodes or logical table fields with other statuses are not affected.

    Rerun all failed instances

    Dataphin automatically selects and reruns nodes or logical table fields in the current folder with a failed status. Nodes or logical table fields with other statuses are not affected.

  • Level 3: Supported actions for a single backfill data instance.

    Note
    • Click the image button in the Running status column to quickly filter instances by their running status. Running statuses include: success, failed, running, waiting for scheduling time, throttling, not started, and waiting for scheduling resources.

    • Click the image button in the Instance name column to search for backfill data instances within the current backfill task.

    • Click the image.png icon in the Scheduled Time, End Time, or Runtime column to sort the backfill data instances by Scheduled Time, End Time, or Runtime in ascending or descending order.

    The operations supported for backfill data instances of integration, compute, and modeling tasks are the same as for their corresponding periodic instances. For more information, see:

Batch operations for submitted instances

Batch operations for submitted instances differ from those for periodic instances. The following table describes the available batch operations.

Actions

Description

Rerun

After selecting multiple backfill data instances, choose Rerun all failed instances, Rerun all final-state instances, or Force rerun of all instances at the bottom of the list. Rerunning an instance directly updates its data. If a downstream node failed to start because the current instance failed, it runs automatically after a successful rerun.

  • Rerun all failed instances: Reruns nodes with a failed status.

  • Rerun all final-state instances: Reruns nodes with a failed or success status.

  • Force rerun of all instances: All nodes or fields in any state can be forcibly rerun, except for logical table instances whose models have been modified.

Terminate

Instances in any state except success or not started can be terminated. After termination, the instance running status changes to failed. Terminating an instance node prevents its downstream nodes from running.

Note

If your selection includes instances with a success or not started status, the batch terminate operation is not supported.

The terminate operation is typically used in the following scenarios:

  • You need to terminate an instance due to a Dataphin anomaly or an operational error.

  • An instance has a running status but has not produced data for a long time. You can manually terminate the run and check the run logs to troubleshoot the issue.

Set to Successful and Continue Scheduling

Manually set the status of multiple instance nodes to success when their current status is failed or not started. This allows them to continue participating in scheduling. Downstream instances blocked only by the current instance failure will begin to run.

Important

Downstream instances that depend on data from the current instance might encounter errors. Assess the risks before proceeding.

Pause

Only instances with a status of not started, waiting for scheduling time, or throttling can be paused.

Note

When you use the pause operation, it only affects instances that can be paused. The system automatically skips instances that cannot be paused.

Resume

Only paused instances can be resumed.

Note

When you use the resume operation, it only affects paused instances. The system automatically skips instances that cannot be resumed.

Modify priority

Click the image icon and select Modify Priority. In the Batch modify priority dialog box, change the priority of the selected tasks. You can choose Highest, High, Medium, Low, or Lowest.

Download all

After selecting multiple instances, click the image icon at the bottom of the list and choose Download All. This action downloads information for all instances across all pages in the current list, including any filtered results.

Operations for backfill DAG nodes

Click the name of a backfill data instance to open its DAG. The DAG shows the relationships between backfill nodes and their dependencies for each business date.

Dataphin supports cross-project node management. To manage a backfill data instance node from another project, you need view and operational permissions for the project where the instance resides.

Note

When viewing a DAG, the instance object list displays the object name and scheduled run time. Hovering over an instance object shows the node name, node ID, scheduled time, and runtime.

The operations supported for backfill DAG nodes are the same as for periodic instances. For more information, see: