Loading

Salesforce Platform: Deployment or Validation Progress Resets After App Server Restart

Дата публикации: Mar 25, 2026
Описание

After the app server restarts, the component and apex test classes circles can be seen starting from the beginning. The users can see this behavior in the deployment status. 

 

What Is an App Server Restart?

Salesforce runs on a multi-tenant infrastructure (a system where multiple customers share the same application servers, with data kept separate and secure). Periodically, Salesforce performs planned or unplanned app server restarts — reinitialization events for the application server instances that host your org. These restarts can occur during:

- Salesforce release deployments (major, minor, or patch updates)
- Routine server maintenance windows
- Unplanned infrastructure events

 

Example Scenario

A Salesforce administrator initiates a change set deployment to production containing 150 metadata components and 100 Apex test classes. After 80 components have been successfully deployed and 40 Apex test classes have passed, a Salesforce app server restart occurs — triggered by a routine Salesforce patch release. When the administrator checks the Deployment Status page, they notice the component counter has reset to "0 of 150." Concerned that the deployment has failed, they contact Salesforce Support. Support confirms this is expected behavior: the component deployment restarts from the beginning to ensure all changes are applied consistently, while the Apex test class execution continues from test class 41. The deployment completes successfully with no data loss or errors.

Решение

No Action Required — This Is Expected Behavior

No action is required from the administrator. The behavior described above is working as designed by Salesforce.

Why the Component Progress Resets

When an app server restart occurs mid-deployment, Salesforce automatically re-processes all metadata components from the beginning of the deployment queue. This is intentional — it ensures that every component is fully and correctly applied in the correct order, preserving the integrity of the deployment. The reset in the progress counter does not mean previously deployed components are lost or need to be resubmitted.

Why Apex Test Execution Does Not Reset

Unlike component deployment, Apex test class execution state is preserved across app server restarts. Salesforce stores the test execution progress independently, so completed test class results are retained and execution resumes from the last successfully completed test — reducing redundant processing and overall deployment time.

What to Monitor

While no action is required, administrators should monitor the Deployment Status page (Setup > Deployment Status) to confirm:

- The component deployment progress continues after the reset and eventually reaches 100% completion.
- Apex test class execution continues progressing from where it paused.
- The overall deployment or validation status eventually shows "Succeeded."

Дополнительные ресурсы

-  Monitor Deployments in Salesforce: https://help.salesforce.com/s/articleView?id=sf.deploy_monitoring.htm&type=5
- Deploy Metadata with Change Sets: https://help.salesforce.com/s/articleView?id=sf.changesets.htm&type=5
- Apex Testing Overview (Salesforce Developer Documentation): https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_intro.htm
- Salesforce Maintenance and Trust Status: https://status.salesforce.com

Номер статьи базы знаний

000395077

 
Загрузка
Salesforce Help | Article