# IOTA queued or 0 tokens/s: wait or restart?

Keep training enabled when a recent response says queued and there is no stop or crash evidence. Zero throughput alone is not a failure diagnosis; check timestamps before restarting.

- Canonical: https://iotahome.site/en/learn/iota-queue-and-zero-throughput
- Publisher: IOTA Watch
- Topics: IOTA
- Published: 2026-10-17
- Updated: 2026-10-22

## At a glance

Keep training enabled when a recent response says queued and there is no stop or crash evidence. Zero throughput alone is not a failure diagnosis; check timestamps before restarting.

## Check before restarting

[Check device status](https://iotahome.site/en/app) · [Manage paired Macs](https://iotahome.site/en/machines)

## What you see / what to do

| Observation | Next step |
| --- | --- |
| Recent queued response / rank | Keep enabled and watch the next fresh update; rank is not an ETA. |
| Fresh positive throughput | The official sample reports contribution; local logs establish current activity. |
| Stale heartbeat / failed fetch | Check agent and connectivity; unknown is not offline or zero contribution. |
| Stopped training / exit record | Use the stopped-training guide and inspect logs before recovery. |

## Why do queue rank and the project badge disagree?

Queue rank comes from local registration logs through the paired agent; the project badge comes from official rosters. The agent accepts queue records after the current worker launch and within five minutes; online also requires a heartbeat within 90 seconds. A rank beside Not in roster calls for comparing sources, not declaring the Mac offline.

## Why am I queued when the network has spare seats?

Network-wide free seats are not seats your miner is eligible for. Run conditions, eligibility and refresh times differ. The next free seat is not promised to you. Compare the timestamped capacity on this page with [tiers and eligibility](https://iotahome.site/en/learn/iota-run-tiers).

## When should I intervene?

Record app version, run ID, queue timestamp and recent logs. Do not repeatedly restart, reinstall or change ID for a rank jump, low CPU or zero throughput alone. A returned Start training button, a fresh exit log or a stopped worker needs the [recovery checklist](https://iotahome.site/en/learn/iota-training-stopped-auto-recovery).

## Common questions

### Why do queue rank and the project badge disagree?

Queue rank comes from local registration logs through the paired agent; the project badge comes from official rosters. The agent accepts queue records after the current worker launch and within five minutes; online also requires a heartbeat within 90 seconds. A rank beside Not in roster calls for comparing sources, not declaring the Mac offline.

### Why am I queued when the network has spare seats?

Network-wide free seats are not seats your miner is eligible for. Run conditions, eligibility and refresh times differ. The next free seat is not promised to you. Compare the timestamped capacity on this page with tiers and eligibility.

## Sources and implementation

- [Macrocosmos · TAH user guide](https://docs.macrocosmos.ai/product-and-services/tah/tah-user-guide)
- [Macrocosmos · Scoring, Rewards & Kicking](https://docs.macrocosmos.ai/subnets/subnet-9-iota/scoring-rewards-and-kicking)
- [IOTA Watch · Agent 1.0.8 recovery implementation](https://github.com/molimao/iota/blob/main/scripts/device-agent/iota_watch_agent.py)