> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/deployments/update-deployment/view-deployment-progress/abort-a-deployment.md).

# Abort a Deployment

Stop the update flow for a whole deployment or for a single device only.

Once you [have deployed a software update flow](/features-new-ui/deployments/update-deployment.md) in JFrog Connect, you can abort it at any time.

You can abort the deployment to a specific device or you can abort an entire deployment. 

The abort options are in the [Detailed Deployment Information](/features-new-ui/deployments/update-deployment/view-deployment-progress/detailed-deployment-information.md) display. Do the following:

1. Go to **Deployments** in the left menu and click the **Runs** tab.
2. In the Runs table, in the row of the relevant deployment, click on the numbers the **Status** column.

### Abort Single Device

You can abort a deployment to a specific device when the deployment is in Pending or In Progress state. 

To abort the deployment to a specific device:

* Go to the row of the device in the Device Status table and click **Abort**. 

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/B15sRAqp7Dq7eGsxHqiR/abort-a-deployment-nui-01.png" alt="" width="563"><figcaption></figcaption></figure></div>

### Abort Whole Deployment

To abort all devices in a deployment:

* Click **Abort Deployment** on the bottom right.&#x20;

The Abort action stops the deployment on devices that are in Pending or In Progress state. Abort does not affect devices that are already in Succeeded or Failed state.

## What’s Next?

Learn about running [graded deployments](/features-new-ui/deployments/update-deployment/best-practice-deploy-in-groups.md).


---

# 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.connect.jfrog.io/features-new-ui/deployments/update-deployment/view-deployment-progress/abort-a-deployment.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.