> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.3/operation-guide/background-tasks/manage-background-tasks-using-the-gui.md).

# Manage background tasks using the GUI

The GUI provides a background tasks page displaying the active background tasks and their details, including the duration since they last started, state, phase, and progress percentage. 

If other background tasks or activities are of higher priority, you can pause and resume the background task later.

The abort action is applicable for some of the tasks, such as checking metadata integrity. For other tasks, such as downloading a filesystem or a snapshot, squashing a filesystem, and detaching object storage from a filesystem, the abort action is not applicable. To abort such a task, delete its entity.

<figure><img src="https://content.gitbook.com/content/lGKb8DZItQx3Jy6unw5f/blobs/yhZYQ5XaLShgtdZoSoVw/wmng_bkg_tasks.png" alt=""><figcaption><p>Background Tasks</p></figcaption></figure>

**Procedure:**

1. From Monitor, select **Background Tasks**.
2. To pause a task, select **Pause**. (The button toggles to **Resume**.)
3. To resume a paused task, select **Resume**.
4. To abort a task, select **Abort**.


---

# 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.weka.io/4.3/operation-guide/background-tasks/manage-background-tasks-using-the-gui.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.