View and manage instances to be submitted - Dataphin - Alibaba Cloud Documentation Center

Instances to be submitted are generated when an auto triggered node initiates a scheduled data backfill operation. These instances will generate runnable instances in future time periods and submit them for data backfill execution. On the instances to be submitted page, you can perform operations such as pause, resume, and retry on the instances to be submitted. This topic describes how to view and manage instances to be submitted.

Instances to be submitted entry

On the Dataphin home page, single click the top menu bar Development > Task Operation And Maintenance.
In the O&M Center, single click Data Backfill Instance in the left-side navigation pane to access the data backfill instance page.
On the Data Backfill Instance page, single click the Instances To Be Submitted tab.

Introduction to the instances to be submitted page

The instances to be submitted page features a search and filter area, a list of instances to be submitted, and a batch operation section. You can perform various O&M operations on this page.

Area	Description
①Search and filter area	Primarily filters instances for the current account. The filter supports narrowing down instances by entering the instance object name or ID, ideal for locating specific instances when the ID or name is known. Filter options include: Submitted By Me: Filters instances submitted by the current account when selected. Scheduled Run Time: Allows filtering of instances for today, future dates, or a specific time range.
②Filter area	Click the filter to expand the filter options, which include: Scheduling cycle: Filters by the scheduling cycle type of the instance, supporting Day, Week, Month, and multiple selections. Submitter: Filters by the submitter of the instance. Scheduled run time: Filters by the scheduled run time of the instance, supporting Today, Today And Later, or A Specific Time Period. Status: Filters by the status of the instance, supporting Instance To Be Submitted, Instance Generation Failed, Paused, Submitting, Instance Generation Successful. Instance submission: Instances will be created and queued for future data backfill periods. Note Instances for periodic data backfill are scheduled to be queued at 23:00 the day before the intended execution time. Instance generation failure: Instances may fail to generate due to system errors or other issues. If this occurs, a rerun can be initiated. For detailed instructions, see rerun instances to be submitted. Paused: When paused, no new data backfill instances will be created, but existing instances remain unaffected. To continue, a resume operation is required. For instructions, see resume instances to be submitted. Submitting: Instances are currently being processed to generate runnable data backfill instances. Instance generation success: Runnable data backfill instances have been successfully created. To view these instances, please refer to the generated instances section. For more information, see view and manage submitted instances. To reset filters, click to clear all conditions and revert to default settings.
③Instances to be submitted list	The page displays a list of instances initiated by auto triggered nodes, including details like the data backfill instance name, data timestamp, scheduling cycle, scheduled run time, status, submitter, data backfill node, and available O&M operations: Save as data backfill node: Converts a single instance into a data backfill node with a click on . For details, see create a new data backfill node. Resume: Resumes paused instances with a click on . Note Upon resuming paused instances for submission, the system checks if the scheduled runtime for the instance has elapsed. If so, it automatically generates data backfill instances to perform the data backfill. Pause: Pauses instances in the 'to be submitted' status with a click on . Note Pausing will prevent the generation of new runnable data backfill instances, but existing instances will remain unaffected. Rerun: Reruns instances with a failed generation status with a click on .
④Batch operation area	The batch operation area allows for processing multiple instances simultaneously, enhancing operational efficiency: Batch resume: Resumes multiple instances at once. Batch pause: Pauses multiple instances at once. Note Pausing will prevent the generation of new runnable data backfill instances, but existing instances will remain unaffected.