> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/pam-with-devolutions-cloud/privileged-access-reports/tasks.md).

# Tasks

Track password reset task status in Devolutions Cloud PAM vaults, filtering by entry name and provider to review full status history for each task.

The ***Tasks*** report allows you to monitor the status of password resets in specific PAM vaults. It essentially follows the password resetting flow by giving you the actions that the Devolutions Cloud Services performed.

Each entry in the task list corresponds to a separate password reset action. You can filter them by ***Entry name*** or ***Provider*** to search for password resets done on specific entries.

The ***Status*** column shows the status of the password reset, which can either be ***Created***, ***Pending***, ***In Progress***, ***Completed***, ***Canceled***, or ***Failed***. As with the entry name and provider, you can filter the status column to see only tasks with certain statuses.

Hover over the icon in the status cell to see the complete history of that task's status.

{% hint style="info" %}
Password reset logs can also be found in the ***Logs*** section of the [privileged account](/pam/pam-with-devolutions-cloud/privileged-accounts.md)'s dashboard.

In the [***Activity Logs Report***](https://docs.devolutions.net/cloud/web-interface/reports/logs), you can see logs pertaining to vault and PAM vault activity.
{% endhint %}


---

# 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.devolutions.net/pam/pam-with-devolutions-cloud/privileged-access-reports/tasks.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.