# SonarCloud does not cleanup it's comments anymore on a PR in Azure DevOps

**URL:** <https://community.sonarsource.com/t/sonarcloud-does-not-cleanup-its-comments-anymore-on-a-pr-in-azure-devops/10246>\
**Category:** SonarQube Cloud\
**Tags:** azuredevops-services, pull-request\
**Created:** [May 29, 2019, 8:50am UTC](https://community.sonarsource.com/t/sonarcloud-does-not-cleanup-its-comments-anymore-on-a-pr-in-azure-devops/10246 "2019-05-29T08:50:49Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pconnor](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/pconnor/32/984_2.png) [@pconnor](https://community.sonarsource.com/u/pconnor)\
**Post date:** [May 30, 2019, 9:38am UTC](https://community.sonarsource.com/t/sonarcloud-does-not-cleanup-its-comments-anymore-on-a-pr-in-azure-devops/10246/6 "2019-05-30T09:38:30Z")

</div>

We’ve had this issue since the 15th of April. I reported it in this thread here:

> [@Azure DevOps PR decoration undocumented behavior?](https://community.sonarsource.com/t/azure-devops-pr-decoration-undocumented-behavior/8096/2):
>
> I’m not aware of such limit. Maybe @Julien_HENRY can give more insights. When you say “when we set the status in the PR to WontFix”, you mean when you do it in Azure DevOps UI? I guess the idea is to not “pollute” too much the PR with useless comments (when issues are fixed, there’s no more problem). You would expect the comment to be set to “Closed”?

Does this happen for all your pull requests or just some of them? I’m pretty sure with us it is quite sporadic and to when it decides to delete them and when it decides to keep them.

---

_[View the full topic](https://community.sonarsource.com/t/sonarcloud-does-not-cleanup-its-comments-anymore-on-a-pr-in-azure-devops/10246)._