> 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.md).

# View Deployment Progress

Once you have [launched a deployment](/features-new-ui/deployments/update-deployment.md) in JFrog Connect, you have full visibility into the status of the software update. This includes a brief summary of all deployments in the Runs table and a detailed view for each deployment.

To view the progress of your most recent deployments:

* Go to **Deployments** in the left menu and the **Runs** tab. The Runs table shows you the progress summary of your software deployments.

<div align="left"><figure><img src="/files/cCNLPS0vwDcYIBaUW85K" alt=""><figcaption></figcaption></figure></div>

The Runs table shows the following information:

* **Deployment ID**: Unique identifier of the deployment and phase. For a [phased deployment](/features-new-ui/deployments/update-deployment/set-phased-rollout.md), a one-digit suffix indicates the phase. Values 1-3 indicate the download phases, and 4 indicates a rollback phase.&#x20;
* **Deployment Tag**: The deployment tag name, if one was configured, and the deployment tag version.
* **Start Time (GMT)**: The date and time when the deployment started.
* **Type**: Indicates that this is a Regular or a Phased Rollout.
* **Flow Name**: The name of the update flow used for the deployment.
* **Vulnerabilities**: A brief listing of the vulnerability statuses detected according to the latest [vulnerability scan](/features-new-ui/deployments/update-flow/vulnerability-scans.md). Hover your cursor over the CVE Severity to see the tally of the CVE Severities of vulnerabilities detected. Click the CVE Severity to find out more information about the CVEs.
* **Status**: The number of devices in each deployment status. Hover over the numbers to see the popover with the status names. Click on the numbers to see the [Detailed Deployment Information](/features-new-ui/deployments/update-deployment/view-deployment-progress/detailed-deployment-information.md).

<div align="left"><figure><img src="/files/map2PyZvUDwCldigwwoM" alt="" width="223"><figcaption></figcaption></figure></div>

### Refresh

To refresh the data manually, click the refresh button on the upper right.

### Filter

If you do not see the deployments you are looking for, click the filter button on the upper right and use the filter to change the deployments in view.

## What’s Next?

Learn more about viewing the [Detailed Deployment Information](/features-new-ui/deployments/update-deployment/view-deployment-progress/detailed-deployment-information.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.connect.jfrog.io/features-new-ui/deployments/update-deployment/view-deployment-progress.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.