# Automatic analysis can't be disabled

**URL:** <https://community.sonarsource.com/t/automatic-analysis-cant-be-disabled/75389>\
**Category:** SonarQube Cloud\
**Tags:** coverage\
**Created:** [November 1, 2022, 4:23pm UTC](https://community.sonarsource.com/t/automatic-analysis-cant-be-disabled/75389 "2022-11-01T16:23:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![logan](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/logan/32/38662_2.png) [@logan](https://community.sonarsource.com/u/logan)\
**Post date:** [November 1, 2022, 4:23pm UTC](https://community.sonarsource.com/t/automatic-analysis-cant-be-disabled/75389/1 "2022-11-01T16:23:25Z")

</div>

We just added our private GitHub project to SonarCloud and it was configured by default to use automatic analysis. I’m attempting to update our configuration to use GitHub Actions so that we can configure test coverage reporting, but I’m unable to update the project to toggle automatic analysis off; instead, an error pops up saying “Project doesn’t exist”.

Steps to Reproduce:

1. On the project dashboard, click Overview.
2. On the “Choose your Analysis Method” page, click “With GitHub Actions\>”
3. Follow steps 1-3 as presented.
4. On Step 4 (“Disable automatic analysis”), click the toggle to disabled.
5. The slider toggles back to enabled and the error message appears at the top of the screen.

It seems like the `main` branch is still being analyzed (and has perhaps been stuck analyzing since early yesterday), so maybe that’s the issue? I don’t know how to stop any ongoing branch analysis that might be holding this up though.

---

<div class="post-metadata">

**Author:** ![Lucas\_Paulger](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/lucas_paulger/32/30207_2.png) [@Lucas\_Paulger](https://community.sonarsource.com/u/Lucas_Paulger)\
**Post date:** [November 7, 2022, 8:59am UTC](https://community.sonarsource.com/t/automatic-analysis-cant-be-disabled/75389/5 "2022-11-07T08:59:30Z")

</div>

Greetings Logan,  
Is this project by chance a mono repo? If that’s the case this is a known bug (see an old thread [Cannot Disable Automatic Analysis - #4 by srstedman](https://community.sonarsource.com/t/cannot-disable-automatic-analysis/54332/4) which includes a workaround for now)

If that’s not the case I can help understand the problem more.

---

<div class="post-metadata">

**Author:** ![logan](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/logan/32/38662_2.png) [@logan](https://community.sonarsource.com/u/logan)\
**Post date:** [November 8, 2022, 3:35pm UTC](https://community.sonarsource.com/t/automatic-analysis-cant-be-disabled/75389/6 "2022-11-08T15:35:52Z")

</div>

No, it’s not configured as a monorepo. I ended up removing the project, adding the `sonar-project.properties` file to our repo, and then re-adding the project to SonarCloud. It looks like that successfully prevented the automatic analysis from running and we’re correctly using CI-based analysis now.

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/system/32/31083_2.png) [@system](https://community.sonarsource.com/u/system)\
**Post date:** [November 18, 2022, 1:25pm UTC](https://community.sonarsource.com/t/automatic-analysis-cant-be-disabled/75389/8 "2022-11-18T13:25:02Z")

</div>

Closed on November 18, 2022, 1:25pm UTC

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.