> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/queues/queues-overview.md).

# Queues overview

Queues are the operational surface of the workflow. Task Queue shows individual work availability and ownership; Batch Queue provides processing and grouped operational context.

{% hint style="info" %}
**Use this area when:** you need to allocate work, inspect backlog, prioritize cohorts, recover failures, or understand why a user cannot start a task.
{% endhint %}

### How this area fits into production

```mermaid
flowchart TB
  A["Workflow stage"]
  B["Task Queue"]
  C["Assignment + priority"]
  D["Workbench action"]
  E["Next stage"]
  F["Batch Queue processing"]
  A --> B
  B --> C
  C --> D
  D --> E
  F -. supports .-> B
```

![Unitlab Task Queue](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2FNuZoKkKYJ9eoN6ckUKWT%2Ftask-queue.png?alt=media\&token=698abe91-80e4-461c-9837-9874a5b22451)

*The queue should make stage, status, priority, assignee, and valid actions visible enough for operators to work without a separate spreadsheet.*

### What this area controls

The project Queue page has two URL-persisted tabs with different purposes:

| Queue           | Default? | Unit represented                          | Primary action                  |
| --------------- | -------- | ----------------------------------------- | ------------------------------- |
| **Task Queue**  | Yes      | One workflow work item waiting in a stage | Manage Workflow / open work     |
| **Batch Queue** | No       | One upload or import action               | Upload data / inspect ingestion |

### Start with the right page

| Decision                             | Production guidance                                                        |
| ------------------------------------ | -------------------------------------------------------------------------- |
| Operate individual work              | Use Task Queue.                                                            |
| Monitor grouped or asynchronous work | Use Batch Queue.                                                           |
| Allocate fairly                      | Configure assignment, claiming, and priority.                              |
| Change many items                    | Use filters and bulk actions only after reviewing the resolved target set. |
| Recover exceptions                   | Inspect failed, invalid, unassigned, or stalled cohorts.                   |

### Operating boundary

* Queue state reflects workflow state; it does not replace the workflow graph.
* Invalid annotation, rejected review, and processing failure are different conditions.
* Priority should express an approved business rule, not hidden personal urgency.

### A production-ready handoff

Every visible backlog has an owner, priority rule, service expectation, valid action, exception path, and reconciled count.