# Issues being report from old code (outside the New Code threshold) **URL:** \ **Category:** SonarQube Cloud\ **Tags:** new\_code, sonarqube-cloud\ **Created:** [December 16, 2021, 12:53am UTC](https://community.sonarsource.com/t/issues-being-report-from-old-code-outside-the-new-code-threshold/55074 "2021-12-16T00:53:07Z")\ **Posts on this page:** 1\ **Showing post:** 5
**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:** [December 17, 2021, 4:10pm UTC](https://community.sonarsource.com/t/issues-being-report-from-old-code-outside-the-new-code-threshold/55074/5 "2021-12-17T16:10:27Z")
Hey @caleb.chenoweth We have a hunch about what’s going on, and it relates to this change the other day: > [@A new approach to analyze TypeScript projects](https://community.sonarsource.com/t/a-new-approach-to-analyze-typescript-projects/54897): > > Hello TypeScript developers, If you see new issues raised on files that were not visible before on SonarCloud, this is expected. We made a change in our approach to scan TypeScript projects to be sure all .ts files used in your projects are really scanned. The previous approach was having some limitations so that [files not referenced in tsconfig were not analyzed](https://github.com/SonarSource/SonarJS/issues/2073). The TypeScript analyzer also supports [directories in “references” in tsconfig](https://github.com/SonarSource/SonarJS/issues/2815), which also contributes to have all your .ts files a… SonarCloud is usually quite good at recognizing new files and making sure the issues that are raised get backdated properly. But when a file has been _indexed_ by SonarCloud but not _analyzed_, this doesn’t work. So when we introduce a change that expands the scope of what files are analyzed in the set of previously indexed files, issues aren’t backdated. This obviously isn’t ideal, and there’s no reasonable workaround to recommend right now. It comes in other flavors as well (when a first analysis is run without NodeJS installed, JS/TS/CSS files are indexed but not analyzed. When this is fixed, those files aren’t considered new and issues aren’t backdated). I’ve flagged this internally to see what, if anything, should be done next… and, a lot of us are about to be on holiday. So bear with us. Thanks for raising it here. --- _[View the full topic](https://community.sonarsource.com/t/issues-being-report-from-old-code-outside-the-new-code-threshold/55074)._