After a lifecycle action in SAE—such as deploying, starting, scaling out, or scaling in an application—you can open the change record to review each sub-step and how long it took. Use change records to monitor deployment progress in real time, audit historical activity, and diagnose failures.
View the current change status of an application
When you create or update an application, the change record appears in real time. The following example uses application deployment.
In the SAE Applications list, select the target region and namespace at the top, then click the target Application ID.
On the Basic Information page, click Deploy Application, modify the configuration, set the release policy as needed, and click OK.
At the top of the Basic Information page, click Change Details to open the change record.
For a breakdown of each sub-step and its duration, see Release record time consumption visualization.
View historical change records
In the SAE Applications list, select the target region and namespace at the top, then click the target Application ID.
In the left navigation pane, click Change Records to see all release records.
Filter by type: Click the drop-down list next to the release record count and select a type. The default type is Deploy Application.
Open a release record: In the Actions column of the target record, click Change Details.
Release records are stored for a maximum of three months.
Release records
Summary statistics
The Change Records page summarizes release activity across all record types.
Release record type: Filter by type from the drop-down list next to Number Of Release Records to see the count of successful and failed records for each type.
Time consumption: View the average and maximum duration for release records of the same type.
Top 5 sub-steps by time consumption: For each release record type, the system identifies the five sub-steps with the longest average execution time. For details, see Release record time consumption visualization.
Release record details: In the Actions column of a record, click Change Details to open its sub-step breakdown.
Release record time consumption visualization
The change detail view shows each sub-step, its category, and how long it ran.
Sub-step categories:
Platform-side: Displayed in black font. These sub-steps are performed by the SAE platform.
User-side: Displayed in blue font. For platform-side deployments, the font for child steps is blue.
Some sub-steps run concurrently. The duration shown to the right of each sub-step name reflects its individual execution time.
If an application configuration error occurs during a sub-step, an error message appears inline. Fix the configuration and redeploy the application.
The following table describes each sub-step.
| Sub-step | Category | Description |
|---|---|---|
| Build Image | Platform-side | When you deploy using a code package, SAE builds an image from the package and pushes it to an Alibaba Cloud private image repository. This repository is managed by the system. |
| Initialize Environment | Platform-side | Confirms the namespace and makes sure all environment resources are ready. |
| Create Or Update Deployment Configuration | Platform-side | Creates or updates the application's base configuration: image address, resource specifications, and policies. |
| Execute Deployment Steps | Platform-side | Starts the deployment task, including network configuration and resource pre-allocation. |
| Release Instances | Platform-side | Creates instances (pods). Each instance goes through resource scheduling, volume mounting, init container startup, image pull, and container startup. Multiple instances are created independently. |
| Resource Scheduling | Platform-side | The scheduler assigns each pod to a node that meets the application's CPU, memory, and network requirements, then binds the pod to that node. |
| Instance Preparing | Platform-side | The node reserves resources for the pod and initializes its environment: network, storage, and init containers. |
| Start Pulling Image | Platform-side | Pulls the application image from the private image repository. For image-based deployments, the image address is used directly. For code package deployments, the address format is Image Source/Image Repository Name/Image Tag. |
| Image Pull Finished | Platform-side | The image pull completed. If the pull failed, an error message appears. |
| Container Created Successfully | User-side | The application container was created. If creation failed, an error message appears. |
| Container Process Started | User-side | The container process started. If startup failed, an error message appears. |
| Instance Ready | User-side | The instance passed the health check and is ready to serve traffic. |
Troubleshooting
If an error occurs during application creation or deployment, an error message appears in the corresponding release record sub-step.
Health check failure
The instance fails to start due to a liveness check failure.
Where to view the error:
In the release record sub-step:
In Application Events:
Possible causes:
The health check is configured with an incorrect port.
The network configuration is incorrect.
Solution:
Identify the application instance port and confirm the health check is configured with the correct port.
Confirm the network configuration is correct.