# HouseKeeping of inactive pull requests not working **URL:** \ **Category:** SonarQube Server / Community Build\ **Tags:** housekeeping, pull-request, sonarqube\ **Created:** [September 7, 2022, 11:51am UTC](https://community.sonarsource.com/t/housekeeping-of-inactive-pull-requests-not-working/71093 "2022-09-07T11:51:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![fransastre](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@fransastre](https://community.sonarsource.com/u/fransastre)\ **Post date:** [September 7, 2022, 11:51am UTC](https://community.sonarsource.com/t/housekeeping-of-inactive-pull-requests-not-working/71093/1 "2022-09-07T11:51:03Z")
Hello, We are using SonarQube 9.4 community in a dedicated server, also using ‘Community Branch Plugin’ v1.11.0 to add pull request information. Recently we realize that we are storing pull requests information since we started using the plug-in, almost a year ago. But in the HouseKeeping section, in the ’ Number of days before purging inactive branches and pull requests’ we have the default value of _30 days_, so we thought that after that period of time, scans from inactive PRs older than that, would be removed. The issue is that some projects may have +300 PRs scan stored, most of them older than 6 months, that are creating a performance issue while scanning or simply accessing the project information. Are we missing something? Are the PRs info created with the ‘Community Branch Plugin’ not affected by the cleaning setting commented above? Thanks in advance. Fran. ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [September 7, 2022, 5:16pm UTC](https://community.sonarsource.com/t/housekeeping-of-inactive-pull-requests-not-working/71093/2 "2022-09-07T17:16:03Z")
Hi, That plugin isn’t supported here. You should direct related questions to its maintainers.   Ann