# Azure Devops PR Decoration issue: This file no longer exists in the latest pull request changes **URL:** \ **Category:** SonarQube Cloud\ **Tags:** pull-request-decorat, sonarqube-cloud\ **Created:** [March 10, 2022, 8:16pm UTC](https://community.sonarsource.com/t/azure-devops-pr-decoration-issue-this-file-no-longer-exists-in-the-latest-pull-request-changes/59709 "2022-03-10T20:16:34Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\ **Post date:** [March 14, 2022, 9:36am UTC](https://community.sonarsource.com/t/azure-devops-pr-decoration-issue-this-file-no-longer-exists-in-the-latest-pull-request-changes/59709/2 "2022-03-14T09:36:58Z")
Hey there. A user faced a similar issue here: > [@Fixing the root map in a SonarCloud project compared to an Azure Devops / GIT project](https://community.sonarsource.com/t/fixing-the-root-map-in-a-sonarcloud-project-compared-to-an-azure-devops-git-project/55968/9): > > Hi @Colin, No need, I have figured out what was wrong. The Soundcloud project I made was not directly linked to the Azure project, as I also had an UI project which WAS linked to the Azure project. Since then, I figured out the function and use of the Monodevelop projects. With that, I was able to set it up so that both the API and UI point to the same Azure repository, and with that, this problem has been fixed. Can you check that this project is [bound](https://docs.sonarcloud.io/advanced-setup/bound-vs-unbound/) to the repository you expect (the repository where your Pull Requests are being raised)? It means that this link on your SonarCloud project (the one you’re taken to when you click **See it in SonarCloud** ) should take you to the right repository. ![Screenshot 2022-03-14 at 10.35.32](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/4/0/4013bf9bbdcf7e8cbff4b2562abd7bb982efcf36.png) > [@jdinardo](#): > > I’m in the process of rolling out sonarcloud across our applications within our organization, and any time I add the sonar steps to the build pipeline for an application and PR those changes to our repos, sonar cloud will automatically spam the first PR containing any changes with 50+ comments pointing out existing issues that weren’t introduced in the PR. Hm. That shouldn’t be happening. Does this happen even if the target branch of the PR (like `master`) has already been analyzed? --- _[View the full topic](https://community.sonarsource.com/t/azure-devops-pr-decoration-issue-this-file-no-longer-exists-in-the-latest-pull-request-changes/59709)._