> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/troubleshooting-ides/missing-or-differing-results-in-snyk-code.md).

# Missing or differing results in Snyk Code

How to resolve missing or differing Snyk Code results caused by ignore files

## .gitignore and .dcignore files <a href="#gitignore-and-.dcignore-files" id="gitignore-and-.dcignore-files"></a>

* Rename all `.gitignore` and `.dcignore` files to, for example, `.dcignore.bak.`
* Rerun Snyk Code.
* If the result is now better, check the rules in `.gitignore` and `.dcignore` files to see if they cause the ignoring of files.
* Ignores can be analyzed in Jetbrains by enabling debug logging for the Snyk Code logger.
* Ignores can be analyzed in the Language Server by enabling trace logging, for example, by setting the env-variable `SNYK_DEBUG_LEVEL=trace.`
* Enable ignore patterns step-by-step until results are correct, and the only files that are ignored should be ignored.
* If the `.dcignore` is filled with a lot of ignores and was created automatically, it should be emptied. IntelliJ before 2.4.63 added this file automatically when no `.gitignore` was found at the top level. It contained many rules that can interfere with repositories and source files.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/troubleshooting-ides/missing-or-differing-results-in-snyk-code.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.