> 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.2/usage/background-tasks/manage-background-tasks-using-the-cli.md).

# Manage background tasks using the CLI

Using the CLI, you can:

* [View running background tasks](#viewing-running-background-tasks)
* [Limit background task resources](#limit-background-task-resources)
* [Pause/Resume/Abort a background task](#pause-resume-abort-a-background-task)

## View active background tasks <a href="#viewing-running-background-tasks" id="viewing-running-background-tasks"></a>

You can view the active background tasks' status, progress, and description.‌

‌**Command:** `weka cluster task`‌

This command is used for viewing all active background tasks.

Example:

```
# weka cluster task
Type       | State   | Progress | Description
-----------+---------+----------+-----------------------------------------------------------
OBS_DETACH | RUNNING | 94       | Detaching Object Storage `obs_1` from filesystem `default`
```

## ‌Limit background task resources

It is possible to limit the resources being used by background tasks.

The configured limit affects external tasks and internal low-priority asynchronous operations.‌

**Command:** `weka cluster task limits`

This command is used to view the defined limits.

**Command:** `weka cluster task limits set [--cpu-limit cpu-limit]`

This command is used to update the CPU limit.

## Pause/Resume/Abort a background task

If there are other background tasks or activities that are of higher priority, you can pause and later resume the background task, or abort it.&#x20;

**Command:** `weka cluster task pause / resume / abort <task-id>`

This command is used to pause, resume, or abort a specific task process. The `abort` subcommand is not applicable when downloading a filesystem or a snapshot. Instead, delete them directly.


---

# 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.2/usage/background-tasks/manage-background-tasks-using-the-cli.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.