# Asynchronous Task Manager

This module oversees and monitors background tasks that operate independently from the main application flow. Built on the **Celery** framework, an asynchronous task/job queue based on distributed message passing, it focuses on real-time operations while supporting scheduling.

For instance, when a baseline scheduler is created, a corresponding task is automatically generated, which can be monitored and managed within the Asynchronous Task Manager. This ensures that tasks can run asynchronously in the background or synchronously, depending on the requirements.

## **What do you see on the screen**

<table data-header-hidden><thead><tr><th width="162"></th><th width="252"></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong></td><td><strong>Action</strong></td><td><strong>Description/ Example</strong></td></tr><tr><td>Task Name</td><td>No actions can be taken. This field is for viewing purposes only.</td><td><p>Identifies the specific Celery task.</p><p>Example: "Start Configmgmt Uploadjob"</p></td></tr><tr><td>Worker Name</td><td>No actions can be taken. This field is for viewing purposes only.</td><td><p>Displays the Celery worker process name assigned to the task.</p><p>Example: "Infraon"</p></td></tr><tr><td>Description</td><td>No actions can be taken. This field is for viewing purposes only.</td><td>Provides detailed information about the task's purpose and functionality</td></tr><tr><td>Queue Name</td><td>No actions can be taken. This field is for viewing purposes only.</td><td><p>Indicates the Celery message queue associated with the task.</p><p>Example: "upload_jobs"</p></td></tr><tr><td>Status</td><td>No actions can be taken. This field is for viewing purposes only.</td><td>Reflects the current operational state of the task (e.g., "running" or "stopped")</td></tr><tr><td>Last Heartbeat</td><td>No actions can be taken. This field is for viewing purposes only.</td><td><p>Timestamp of the most recent communication between the worker and the Celery broker.</p><p>Example: "38 seconds ago"</p></td></tr><tr><td><strong>Action Icons</strong></td><td></td><td></td></tr><tr><td>Resync Worker</td><td>Users can click to initiate the resync process. A validation step is required to confirm the action.</td><td>Initiates a resynchronization process between the Celery worker and the broker. Requires confirmation</td></tr><tr><td>Stop Worker</td><td>Users can click to stop the worker process. A validation step is required to confirm the action.</td><td>Terminates the Celery worker process, halting task execution. Requires confirmation</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.infraon.io/infraon-help/infinity-user-guide/infraon-configuration/organization/asynchronous-task-manager.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.