# Diagnostics

{% hint style="success" %}
To access workflow and task type settings, you’ll need a **Scale** or **Enterprise** plan.
{% endhint %}

## How diagnostics work

When you open the **Diagnostics** tab, the **Data at task creation** section displays the device’s state as it was recorded when the task was created, based on data from the last 24 hours.

To run a fresh diagnostic check, click **Run diagnostics** in the **Diagnostics & Repair data** section. The diagnostics process takes about **5–6 minutes**, during which the system analyzes the device’s current state. While diagnostics are running, all task actions—such as editing, changing status, or deleting—are disabled.

During diagnostics, a **Cancel diagnostics** button appears in the **Diagnostics & Repair data** block. When diagnostics are canceled or completed, all task actions become available again, and you can re-run diagnostics at any time. When re-run, diagnostic data accumulates but will not exceed a 24-hour window.

After diagnostics finish, the **Diagnostics & Repair data** section displays updated device information, including charts generated from the start of the diagnostic session.

### **Status bar colors**

Status bar colors in the **Diagnostics & Repair data** section reflect the reason determined during diagnostics:

* **Active boards and fans** — green by default
* **Lowhash boards and fans** — yellow
* **Hanged boards and fans** — orange
* **Offline boards and fans** — always red
* **Boards and fans showing** **0**, **no data**, or (for fans) **0/30600/no data** are also displayed in red regardless of status.

### How service center tickets are created

After diagnostics are complete, the device and all its components display checkboxes that allow you to assign repair tickets. Selecting the checkbox for the **device** disables all component checkboxes.

After selecting the necessary components:

1. Click the **wrench icon** in the bulk actions panel.
2. Choose a **service center** (service centers can be added in Settings).
3. (Optional) Select a task manager to create a **related task** in another manager.
4. **Confirm** ticket creation.

If a task manager was selected, a related task creation form will open. Each component ticket is independent. If tickets are created for all components, creating a ticket at the device level becomes unavailable.

Once at least one ticket exists, a **wrench icon** appears next to the device or component. Hovering over it shows a tooltip with details about the ticket, including its lifetime.

If a related task was created, it appears in the **Related tasks** section of both the parent and child tasks.

If you do not replace the ticket with a resolution status, the ticket will carry over into all future tasks for this device until a final status is applied.

### How Component Statuses Are Assigned

After diagnostics, you can assign a status to a device or component from the action menu (three dots). Available statuses:

* **Restored**
* **Repair declined**
* **Repair unsuccessful**

Once a status is set, editing the device/component is blocked.

Status assignment is also possible in **On Hold**. If a component with a ticket is assigned a status, the ticket is removed. If all tickets for the device and its components are deleted, the task automatically moves to **Done**.

### Available actions by task status

* **In Progress** – diagnostics are running; no changes allowed until completion. Tickets and statuses can be assigned afterward.
* **To Do** – editable task. After diagnostics, tickets and statuses are unavailable until moved back to **In Progress**.
* **On Hold** – task is waiting on tickets; you can assign statuses for devices/components with tickets.
* **Done** – final status; all actions completed

### FAQ

<details>

<summary>What happens if I move a task back to To Do after diagnostics?</summary>

The diagnostic data is saved, but assigning tickets or statuses is disabled until moved back to **In Progress**.

</details>

<details>

<summary>How many times can I run diagnostics?</summary>

Unlimited. However, charts only summarize data for the last 24 hours.

</details>

<details>

<summary>What is the On Hold status and why is it needed?</summary>

It’s the state a task enters after tickets are created. Only status assignment for devices or components is available in this mode.

</details>

<details>

<summary>How do I finish a task in On Hold?</summary>

Assign statuses to all components with tickets. Once all tickets are removed, the task automatically moves to **Done**.

</details>

<details>

<summary>How do I create a ticket for a component?</summary>

Select the checkbox for the component or the entire device after diagnostics, click the wrench icon, pick a service center, and confirm.

</details>

***

#### We're always available! <a href="#were-always-available" id="were-always-available"></a>

Chat with us on [Telegram](https://t.me/moondmc_bot).


---

# 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://help.moonone.online/task-managers/diagnostics.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.