# Unable to Trigger a Pipeline build On a non PR branch

**URL:** <https://discuss.circleci.com/t/unable-to-trigger-a-pipeline-build-on-a-non-pr-branch/53151>\
**Category:** Build Environment\
**Created:** [April 22, 2025, 5:26pm UTC](https://discuss.circleci.com/t/unable-to-trigger-a-pipeline-build-on-a-non-pr-branch/53151 "2025-04-22T17:26:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![grndvl1](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/grndvl1/32/25392_2.png) [@grndvl1](https://discuss.circleci.com/u/grndvl1)\
**Post date:** [April 22, 2025, 5:26pm UTC](https://discuss.circleci.com/t/unable-to-trigger-a-pipeline-build-on-a-non-pr-branch/53151/1 "2025-04-22T17:26:58Z")

</div>

Up until today we are able to trigger a branch on a non PR branch. Our typical scenario is we take main cut a release branch then use the triggers to manually trigger a release build. But now CI doesn’t even have the branch name in the popup to even trigger the build. Stupid change on their end broke our ability to cut a release build

---

<div class="post-metadata">

**Author:** ![FernandoAbreu](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/fernandoabreu/32/36150_2.png) [@FernandoAbreu](https://discuss.circleci.com/u/FernandoAbreu)\
**Post date:** [April 28, 2025, 8:26pm UTC](https://discuss.circleci.com/t/unable-to-trigger-a-pipeline-build-on-a-non-pr-branch/53151/2 "2025-04-28T20:26:07Z")

</div>

Thanks for raising this — I’m sorry this change disrupted your workflow.

This behavior is due to a recent update where webhooks marked with “CI Skip” or “Only Build PRs” no longer create pipelines: [Changelog link](https://circleci.com/changelog/ci-skip-and-only-build-prs-will-no-longer-create-pipelines/).

As a workaround, you can trigger a build manually using the [Run Pipeline API](https://circleci.com/docs/api/v2/index.html#tag/Pipeline/operation/triggerPipelineRun). This allows you to start a pipeline even if the branch hasn’t previously had any runs.

Alternatively, you could create a temporary PR to trigger the build, and use `[ci skip]` on subsequent commits until you’re ready for a full build.

I hope that helps!