Pipeline execution fails with ‘Branch not found in repository’ error in AEM Cloud Manager
In Adobe Experience Manager Cloud Manager, a pipeline job can fail to execute when the configured source code branch isn’t found in the connected repository. This failure blocks deployments and appears in the pipeline execution logs with a branch not found error. To fix this issue, verify the configured branch, confirm repository access, and update the pipeline or repository configuration as needed.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Manager (all versions)
Issue/Symptoms
An AEM Cloud Manager pipeline job fails to execute and displays an error indicating that a required branch is not found in the source repository.Failed: Invalid pipeline: 320788. Reason=Branch=release/KP.ORG-AUG.31.2026.R1 not found in repository
- The failure blocks production deployments and can have a business impact.
- The error is observed in the Cloud Manager pipeline execution logs.
Resolution resolution
Follow the steps below to resolve the issue.
- In Cloud Manager, open the failed pipeline’s configuration and note the selected repository and exact branch name.
- In the connected source repository, verify that the branch exists and is available to Cloud Manager.
- If the branch is missing, recreate it with the exact same name or update the pipeline to use an existing branch.
- If the branch exists but Cloud Manager cannot access it, check the repository integration and confirm Cloud Manager has the required access. You may need help from your repository owner or Cloud Manager administrator.
- Save any configuration changes and rerun the pipeline.
- Confirm that the pipeline uses the intended branch and completes without the “Branch not found in repository” error. If the branch exists and is accessible but the error persists, contact Adobe Support with the pipeline execution details.