metadata
title: Troubleshooting code scanning
intro: >-
When analyzing your code with {% data variables.product.prodname_code_scanning
%}, you may need to troubleshoot unexpected issues.
redirect_from:
- >-
/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-your-default-setup-for-codeql
- >-
/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow
- >-
/code-security/code-scanning/troubleshooting-code-scanning/results-differ-between-platforms
versions:
fpt: '*'
ghes: '*'
ghec: '*'
topics:
- Code Security
- Code scanning
- CodeQL
- Repositories
children:
- /advanced-security-must-be-enabled
- /alerts-in-generated-code
- /analysis-takes-too-long
- /automatic-build-failed
- /c-sharp-compiler-unexpectedly-failing
- /cannot-enable-codeql-in-a-private-repository
- /enabling-default-setup-takes-too-long
- /extraction-errors-in-the-database
- /fewer-lines-scanned-than-expected
- /logs-not-detailed-enough
- /no-source-code-seen-during-build
- /not-recognized
- /out-of-disk-or-memory
- /resource-not-accessible
- /results-different-than-expected
- /server-error
- /some-languages-not-analyzed
- /two-codeql-workflows
- /unclear-what-triggered-a-workflow
- /unnecessary-step-found
- /kotlin-detected-in-no-build