> 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/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/finding-states.md). # Finding states The states a Snyk API & Web finding can have During a target scan, the scanner identifies vulnerabilities within the target's URLs. When the scanner discovers a vulnerability, Snyk creates a finding. The state of a finding can change either automatically (by the scanner, as a result of a target scan or re-test) or manually (by user actions). ## Available finding states A finding can have the following states: * **Not fixed** - The scanner found a vulnerability that is waiting to be fixed. The user does not control this state. As long as a target scan or re-test finds the vulnerability, the finding stays in the **Not fixed** state. * **Invalid** - The user marked the vulnerability as invalid. This state results from a user action. Use it to report a false positive. * **Accepted risk** - The user marked the vulnerability as accepted risk. This state results from a user action. Use it to identify vulnerabilities that the user does not consider in need of being fixed. * **Fixed** - The scanner could not find a previously existing vulnerability while running a subsequent target scan using the same profile or a broader one, so it marked the vulnerability as fixed. The user does not control this state. * **Re-testing** - The scanner is re-testing a previously existing vulnerability. This state results from a user action. It can lead to either a **Fixed** vulnerability (if the scanner cannot replicate the vulnerability during the re-test) or a **Not fixed** vulnerability (if the scanner finds it again during the re-test). ## User-controlled vs. scanner-controlled states In summary, the user controls the **Invalid**, **Accepted risk**, and **Re-testing** states, while the scanner sets the **Fixed** and **Not fixed** states. --- # 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/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/finding-states.md?ask=&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.