// troubleshooting guide · azure devops
Azure DevOps Pipeline Not Triggering on Push
- Status
- Ongoing
- platforms:
- Web (Azure Pipelines)
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · azure-devops/pipeline-not-triggering4 FIXES
// quick answer
CI is decided by the YAML in the branch you pushed. Check for trigger: none, branch and path filters, UI trigger overrides and [NO_CI] in commit messages; PR triggers for Azure Repos need branch policies.
Most likely fix: Check the YAML in the pushed branch
How to fix it
// try these in order, the most common fix is first
FIX 1Check the YAML in the pushed branch
- 01Open azure-pipelines.yml in the branch you pushed, not main
- 02Make sure trigger: lists that branch under include and the changed paths aren't excluded
- 03Branch names in filters must match exactly
Did this fix it?FIX 2Remove UI overrides
- 01Pipelines > select pipeline > Edit > ... > Triggers
- 02Under Continuous integration, make sure 'Override the YAML continuous integration trigger from here' is unchecked
Did this fix it?FIX 3Set up PR builds with branch policies
- 01Project settings > Repositories > select repo > Policies > select the target branch
- 02Under Build Validation, add your pipeline
- 03PR triggers in YAML only apply to GitHub and Bitbucket repos
Did this fix it?FIX 4Check settings and commit messages
- 01Check Project settings > Pipelines > Settings for 'Disable implied YAML CI trigger'
- 02Make sure none of the pushed commits contain [skip ci] or ***NO_CI***
- 03Check status.dev.azure.com if triggers stopped across all pipelines
Did this fix it?
Symptoms
You push a commit or open a pull request and no pipeline run starts, while a manual run works fine.
Why it happens
- C-01The YAML file in the pushed branch has trigger: none or filters that exclude it
- C-02Pipeline settings in the UI override the YAML triggers
- C-03'Disable implied YAML CI trigger' is enabled for the org or project
- C-04PR triggers in YAML are ignored for Azure Repos Git
- C-05A commit message contains [skip ci] or ***NO_CI***
- C-06The repository resource lives in another project and needs a UI trigger
// this guide also covers
- azure devops pipeline not triggering
- azure pipelines trigger not working
- azure devops pr trigger not working
Still not working?
If Azure DevOps keeps failing, you're not alone. See every Azure DevOps problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Azure DevOps errors
- Azure DevOps No Hosted Parallelism Has Been Purchased or Granted
- Azure DevOps Pipeline Stuck in Queue (Waiting for an Available Agent)
- Azure DevOps Git Authentication Failed (PAT Not Working)
- Azure DevOps TF401027: You Need the Git 'GenericContribute' Permission
- Azure Pipelines Job Canceled After 60 Minutes
- Azure Artifacts Feed 401 Unauthorized (Unable to Load the Service Index)
- Azure DevOps Service Connection 'Failed to Obtain the JSON Web Token'
- Why Is Azure DevOps Boards So Slow?