If a promotion remains in progress after its deployment succeeds or fails, cancel the
associated request record. You can manually clean up a stalled promotion in Lifecycle Center.
Required Editions
| Available in: Lightning Experience in
Professional (API access required), Enterprise, Performance,
Unlimited, and Developer Editions
|
| Not available in: Government Cloud Plus. Contact
your Salesforce account executive for more details. |
| Not available in: EU Operating Zone. EU Operating
Zone is a special paid offering that provides an enhanced level of data residency commitment.
Lifecycle Center is supported in orgs in the EU that aren’t part of EU OZ, per standard
product terms and conditions. |
| User Permissions Needed |
| To fix a stalled promotion: |
Lifecycle Center Deployment Manager |
-
In the target org, from Setup, in the Quick Find box, enter
Deployment Status, and then select
Deployment Status.
-
Check the recent Lifecycle Center deployment associated with the stalled promotion.
- If the deployment succeeded, the deployment completed but the promotion status wasn’t
updated.
- If the deployment failed, the promotion status wasn’t updated after the error.
Follow the same recovery steps for either result.
-
In your Lifecycle Center org, open Developer Console, and then select the
Query Editor tab.
-
To find the promotion record that’s still in progress, run this query:
SELECT Id, Status, RequestInfoId
FROM DevopsPipelnStgProm
WHERE Status = 'IN_PROGRESS'
-
Copy the value in the RequestInfoId column of the affected record.
-
Replace
<request-info-id> with the copied ID, and then run this query:
SELECT Id, Status, OperationType
FROM DevopsRequestInfo
WHERE Id = '<request-info-id>'
-
Select the returned record, and then click Open Detail Page.
-
On the DevopsRequestInfo record, change Status from
IN_PROGRESS to CANCELLED, and then save your
changes.
Lifecycle Center cleans up the stalled promotion. No other manual cleanup is
required.
-
In Lifecycle Center, refresh the Pipeline Stages view.
The stalled-promotion error no longer appears.