click Data Integration > Offline Maintenance > Instance List, to enter the instance operation and maintenance page. Task instances are instance snapshots generated periodically according to the scheduling configuration. The instance operation and maintenance page displays the operation and maintenance status of cyclic instances associated with different tasks based on the Instance ID. It also supports operations such as runtime monitoring and rerun.
Parameter
Description
Instance ID
The system ID and instance data time generated by the system for each scheduled run of the task
Task Name
Task name to which the current instance belongs
Owner
Responsible person's name for the task configuration
Scheduling Cycle
Details of the cyclic operation plan configured for the task to which the current instance belongs
Instance Type
Periodic Instances: Instances automatically generated and executed based on the task operation plan
Supplementary Instances: Instances generated by manually clicking the supplementary operation
Execution Status
Current instance running status:
Success: The instance has run successfully
Failure: The instance run has failed
Running: The instance is running
Waiting to Execute: Includes wait time, waiting for self-dependence, waiting for scheduling resources, waiting for computing resources, etc
Terminating: The instance on which the termination operation was just clicked
Retry upon Failure: The instance failed on the previous run and is preparing to retry
Retry Count
The number of retry attempts for the current instance
Start Running Time
Last Start Running Time
Running Duration
Total running duration. If the task is not completed, it shows as "-"
Operation
Running Details
Includes instance metrics, logs, and other descriptions.
Rerun
Execute "Success" or "Failed" instances again
Terminate
Force terminate "Pending Execution" or "Running" instances
Mark as Successful
Set "Pending Execution" or "Failed" instances to "Success" status. If the task has a serial self-dependency, setting the current instance to success can trigger the execution of subsequent instances
