> 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/manage-jobs.md).

# Cancel, duplicate, and rename jobs

Cancel active renders, duplicate jobs with all or incomplete frames, and rename jobs.

## Cancel a job

1. In **All Jobs** or an open scene's jobs list, right-click an active job and choose **Cancel Job**. To cancel several, select them and use **Cancel Job** in the action bar below the list.
2. If frames are rendering, choose how to handle them:
   * **Stop them immediately** stops the frames in progress.
   * **Let them finish before canceling** lets those frames finish without starting more frames.
3. Check **I understand that render work already completed is not refundable**.
4. Click **Cancel job** or **Cancel jobs**. Click **Keep** to leave the job running.

You can also open the cancellation window from a job's card, detailed card, table row, **Activity** entry, or an open job's top bar or **Attributes** panel.

{% hint style="warning" %}
Cancellation cannot be undone. Completed render work remains billable. Finished frames stay available, and the canceled job remains in your jobs list.
{% endhint %}

To remove a job from the list, see [Delete projects, scenes, and jobs](/docs/web-app/archive.md).

## Duplicate a job

1. Right-click one job and choose **Duplicate**.
2. If it has incomplete frames, choose **Duplicate with all frames** or **Duplicate only incomplete frames**, then click **Duplicate**. Frames already rendered, including those awaiting approval, are excluded from the incomplete selection.
3. Review the prefilled [Create Job](/docs/web-app/create-a-job.md) form, especially the download options. Settings that cannot be copied from the original job start with the form's default values. Make any changes you need.
4. Click **Create Job** to submit the duplicate.

The form uses the original job's scene version and target. A job with no incomplete frames opens the form directly.

**Duplicate** is also available on job cards, detailed cards, table rows, the action bar for one selected job, **Activity** entries, and the open job's top bar and **Attributes** panel. Icon buttons use the tooltip **Duplicate the job**.

Duplication cannot proceed if the original scene is deleted, expired, or unavailable. Read the reason in **Could not duplicate the job**. If you still have the source file, [upload it](/docs/web-app/upload-scenes.md) and create a job from that scene.

## Rename a job

1. Double-click the job to open it. If its left panel is hidden, click the job name at the top of the page.
2. In **Attributes**, click the pencil beside the name.
3. Enter a name, then click the check button or press Enter. Press Escape or click the cross button to discard the edit.

The saved name also appears in the jobs list.


---

# 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/manage-jobs.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.