<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=539287) </details> <!--IssueSummary end--> ## Context Some customers have reported that pipelines are not triggered when pushing branch refs. In this case, branches are created but will not run pipelines. Pipeline triggering fails intermittently with a "Reference not found" error in `Git::BranchHooksService`. ### What is the current _bug_ behavior? * Pipelines randomly fail to trigger when pushing to branches (5-10 times per day reported by customer). * Sidekiq logs show Git::BranchHooksService throwing "Error creating pipeline" with "Reference not found" errors. * Error occurs even when the branch reference clearly exists in the repository. * Teams must manually push "null" changes to trigger pipelines as a workaround. * Issue appears to be related to cache invalidation problems similar to issue #539287, but affects a different component in the pipeline creation process. * Affects Self-Managed instances under normal load conditions. ### What is the expected _correct_ behavior? * Pipelines should trigger consistently when pushing commits to branches. * Git references should be properly found and validated during the pipeline creation process. * Cache invalidation should not prevent pipeline triggering for valid branch references. * No manual intervention should be required to trigger pipelines for legitimate pushes.