> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/web-app/track-progress.md).

# Track uploads, renders and downloads

Follow uploads, renders and downloads, check errors, and manage Activity and History records.

Click **Open activity panel** at the top right of the app. The **Activity** tab groups work under **Uploads**, **Renders**, **Downloads**, and **Errors**. Click a group heading to expand or collapse it.

## Read the progress

Each entry shows its name and status. Progress bars and details appear when available, such as the amount uploaded or the number of rendered frames. A job can appear in both **Renders** and **Downloads** while approved frames are being saved.

Click an entry to open its scene or job. On a job page, you can inspect [individual frames](/docs/web-app/review-and-approve-frames.md).

Failed entries stay in **Errors**, with a reason when one is available. For example, an interrupted upload shows **Upload Failed** and **Upload was interrupted**. See [upload troubleshooting](/docs/web-app/upload-scenes.md#if-an-upload-does-not-work) or [download help](/docs/web-app/download-frames.md#if-a-download-does-not-work) for the next step.

## Keep Activity in a separate window

On a desktop computer, click **Open in a floating window** at the top of the panel. The separate window offers the same Activity and History controls. Clicking a scene or job there opens it in a browser tab.

If the window does not open, see [Browser support](/docs/help/browser-support.md#floating-activity-window).

## Clear finished entries

Closing the panel or moving to another page does not clear its entries. A job that finishes while you are away remains in Activity until you open it. Jobs waiting for frame review remain so you can find them.

* Click **Remove from Activity** on an entry that is no longer active to dismiss it.
* Click **Remove Idle** at the bottom to clear entries for work that has finished or stopped. Work in progress and jobs waiting for review remain.

These controls clear Activity entries without deleting the scenes or jobs.

## Stop current work

Use an entry's cancel action to stop that upload, render, or download. To stop current work together, click **Cancel All Activity** at the bottom and check the counts in the confirmation.

{% hint style="warning" %}
This includes uploads, renders, and downloads. Before confirming, read the consequences of [cancelling an upload](/docs/web-app/upload-scenes.md#cancel-an-upload) and [cancelling a job](/docs/web-app/manage-jobs.md). Failed entries remain in **Errors** after cancellation.
{% endhint %}

## Look back through History

Switch to **History** at the top of the panel. It lists the scene and job status changes recorded by the app, with their names and times. The same scene or job may have several entries.

History is kept in the current browser across reloads and later visits. Click a record to open its scene or job.

Use **Remove from History** to clear one record, or **Clear History** at the bottom to clear the list. Removing a record does not change the scene or job itself.


---

# 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://know.rendernetwork.com/docs/web-app/track-progress.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.