> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.5.1/guardian/standard-registry/asynchronous-tasks-status.md).
# Asynchronous Tasks Status
Worker Tasks tab displays active user's jobs performed asynchronously by the ‘worker’.
* Tasks can have the following status:
* IN QUEUE - for task which are queued pending activation
* PROCESSING - for task which are being performed (in progress)
* COMPLETE - for tasks completed successfully
* ERROR, Reason: \ - for tasks which did not complete successfully, with the reason for failure.
* Failed tasks (in the ERROR state) can be manually retried or deleted.
* Tasks with COMPLETE status are cleared automatically 30 minutes after execution. The system assumes that tasks which have been in the PROCESSING for longer than an hour have stalled. Guardian automatically re-queues them for another attempt (with IN QUEUE state is displayed in the UI).
Architecturally, all errors (if any) are passed back to the Guardian process that initiated the task (e.g. ‘publish schema’), which may result in the entire execution flow being rolled back. In the case of task manual restart and its successful completion the success status is passed back to the process originally initiated the task.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://guardian.hedera.com/docs/3.5.1/guardian/standard-registry/asynchronous-tasks-status.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.