Merge requests fail, indicating that a branch could not be found
There are a couple issues to look out for:
In rare cases this can be caused by a missing Rule-RuleSet-Branch instance. The easiest solution is to add the branch to an application on the SOR from the branch explorer, and then click the branch to launch the branch landing page. This has been addressed in version 8.5 of the Pega Platform.
As of PDF 4.5 you may see this error if your pipeline's target Application is not build on PegaDevOpsFoundation
This error can occur if an Artifactory repository's host name ends with "/artifactory". This configuration allows the branch archive to be uploaded, but not deployed back to the dev system which results in this error.