Forum Discussion
namratam
Jan 03, 2022Copper Contributor
Azure Devops error-Some recent issues detected related to pipeline trigger
I am getting below trigger error on all the pipelines to the repo- Some recent issues detected related to pipeline trigger. This issue comes even when we create new fresh pipeline and the error ...
- Jan 03, 2022Have seen this same error, too (Yaml pipeline).
Edit -> Settings and pointing the pipeline file to a different yaml, saving, then resaving back resolves the error for us.
I investigated [this SO post](https://stackoverflow.com/questions/67830236/new-pipeline-on-azure-devops-shows-error-message-some-recent-issues-detected-re) but this wasn't the issue. The branch for the trigger already existed correctly.
chriskratochvil
Jan 03, 2022Copper Contributor
Have seen this same error, too (Yaml pipeline).
Edit -> Settings and pointing the pipeline file to a different yaml, saving, then resaving back resolves the error for us.
I investigated [this SO post](https://stackoverflow.com/questions/67830236/new-pipeline-on-azure-devops-shows-error-message-some-recent-issues-detected-re) but this wasn't the issue. The branch for the trigger already existed correctly.
Edit -> Settings and pointing the pipeline file to a different yaml, saving, then resaving back resolves the error for us.
I investigated [this SO post](https://stackoverflow.com/questions/67830236/new-pipeline-on-azure-devops-shows-error-message-some-recent-issues-detected-re) but this wasn't the issue. The branch for the trigger already existed correctly.
- xyz012Jan 09, 2022Copper Contributor
chriskratochvil Any solution have you found for the below issue. Even i am facing the same.
- Ashish_yadavJan 03, 2022Copper ContributorChris, we noticed this as well (replacing the YAML file solves the issue). However, this seems like a bug in MSFT as this error started a few weeks ago without any changes from our end. Would you agree? Any luck getting a response from MSFT on this for a permanent RCA and FIX?