DevOps Center Promotion Fails with CHANGE_REQUEST_VALIDATION – ALREADY_MERGED

We are experiencing an issue when promoting a pipeline stage from Partial Copy to Full Copy in Salesforce DevOps Center.

The work item was successfully promoted to the Partial Copy stage. However, when attempting to promote the Partial Copy stage to Full Copy, DevOps Center immediately displays:

“Promotion Failed – We couldn't complete this task. Try again later, or ask your Salesforce admin for help.”

The promotion does not proceed far enough to run tests or create a normal deployment failure record.

After reviewing the browser Network response, I found the following error:

errorType: CHANGE_REQUEST_VALIDATION

reason: ALREADY_MERGED

reviewReference: 48

stage: Partial Copy

GitHub Pull Request #48 was a previous DevOps Center promotion from PartialCopyBranch to FullCopyBranch and was already successfully merged.

A newer Work Item has since been successfully promoted into PartialCopyBranch, but DevOps Center appears to still be validating or referencing the previously merged PR #48 when attempting the next Partial Copy → Full Copy promotion.

Expected behavior:
DevOps Center should create/use the appropriate change request for the current contents of PartialCopyBranch and allow the promotion to Full Copy.

Actual behavior:
Promotion immediately fails because DevOps Center reports the previous change request as ALREADY_MERGED.

Is there a way to reset or resynchronize the pipeline stage/change request association, or is this a known DevOps Center issue?

Thank you.

Start by reviewing the promotion flow for PartialCopyBranch to FullCopyBranch and how it associates change requests with GitHub Pull Request #48. Use the reported CHANGE_REQUEST_VALIDATION / ALREADY_MERGED response and reviewReference 48 as the reproduction signal. Done means a newer Work Item creates or uses the current change request and the promotion reaches Full Copy without the stale merged-PR error.

Written by the indexing model from the issue text.