forcedotcom / forcedotcom/devops-center-feedback

WI pushed to next stage despite deployment failing

Open
#240 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
61
Forks
2
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Our team is encounting an issue where two separate Work Items seemed to have been successfully promoted to the next stage. In both cases the WI moved to the next stage in the dashboard and version control was also updated in the target stage. However, we soon realized that the two deployments actually failed and the changes themselves were not moved to the target org.
After checking the deployment status in the target org we found in both cases the following error occured:

LIMIT_EXCEEDED: Try deploying again. Your deployment exceeded its maximum retry limit. If you keep seeing this error, please contact Salesforce Customer Support.

We also found that both promotions were initiated at (or close to) the same exact time, which appears to be significant and would help explain the Limit Exceeded error.
Screenshot 2022-12-13 at 2 07 31 PM

What we'd like to know is why the Work Items still moved through the pipeline and why version control was updated in spite of the failed deployments.

**To Reproduce**
We believe this is related to the fact that the two separate work items were attempted to be promoted at the same time from different source orgs.

**Expected behavior**
If a deployment fails, version control should not be updated and the WI should not move into the next stage.

**Screenshots**

**Additional context**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.