> 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/start-scanning/overview-scan-management/actions-on-scans.md).

# Actions on scans

The actions you can take on Snyk API & Web scans

The **Targets** section provides a set of actions to manage scans in Snyk API & Web.

On each line in the **Targets** list, choose the scan action to run for that target. You can also manage scans directly from the target details by clicking the target name.

Snyk provides the following actions to manage scans, regardless of where you are in the product:

| Action         | What it does                                                                                                  |
| -------------- | ------------------------------------------------------------------------------------------------------------- |
| **Scan Now**   | Starts a scan.                                                                                                |
| **Scan Later** | Schedules a scan.                                                                                             |
| **Stop**       | Stops a running scan.                                                                                         |
| **Pause**      | Pauses a running scan. If a scan is paused for seven days without being resumed, Snyk automatically stops it. |
| **Resume**     | Resumes a paused scan.                                                                                        |

Depending on the state of the scan, you can perform the following actions:

* You can only start a scan if no scan is running on that target.
* You can only pause a scan if it is running.
* You can only resume a scan if it is paused.
* You can only stop a scan if it is running or paused.
* You can always schedule a scan.

## Summary of available actions by scan state

| Target scan state    | Available actions                   |
| -------------------- | ----------------------------------- |
| No scan is running.  | <p>Scan Now<br>Scan Later</p>       |
| The scan is running. | <p>Stop<br>Pause<br>Scan Later</p>  |
| The scan is paused.  | <p>Resume<br>Stop<br>Scan Later</p> |

Snyk starts or stops a scan as soon as you select those options. Pausing or resuming a scan can take a while, because the scanner must perform the necessary actions. Pausing and resuming scans is available only for some account plans.


---

# 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/start-scanning/overview-scan-management/actions-on-scans.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.