# Mac online but no rewards: should I restart?

Separate device heartbeat, app processes and official training contribution before taking action.

- Canonical: https://iotahome.site/en/learn/mac-status-and-restart
- Publisher: IOTA Watch
- Topics: IOTA
- Published: 2026-10-15
- Updated: 2026-10-17

## At a glance

Separate device heartbeat, app processes and official training contribution before taking action.

Separate device heartbeat, app processes and official training contribution before taking action.

Online means an agent heartbeat arrived within 90 seconds. A running process does not prove contribution. Queue positions come from local logs and expire after five minutes; a missing position does not prove training has started.

## In queue

Waiting for task assignment. Position comes from recent local logs.

## Awaiting initialization

Official heartbeat reports initializing or frozen. This does not mean the Mac is offline.

## Waiting for training work

Official statistics report zero throughput while the miner remains active.

## Recent compute activity

A recent official heartbeat reports forward or backward computation. Rewards are not confirmed by this signal.

## Weight upload phase

The assigned layer is in its weight upload phase. This does not confirm this Mac has uploaded or earned rewards.

## Partition merge phase

The assigned layer is in its partition merge phase. This is not evidence that training has stopped.

## Official status needs attention

Official heartbeat reports kicked. Check local logs and the project; the cause is not confirmed.

## Process running

Training phase is unconfirmed. Check official throughput for contribution.

## Training process stopped

The app is open. Check its training button or logs first.

## TAH stopped

Start TAH when you want to resume.

## No recent heartbeat

Check sleep, network and the agent on your Mac. Training status is unknown.

## When should I restart?

Check the latest status and the app on your Mac. Start it if stopped. If the app is open but its training process stopped, inspect the training button and logs first. Zero rewards, a queue or stale data alone do not justify restarting. Restart interrupts the current process.

## How do I confirm a restart?

Waiting for device → Dispatched, awaiting result → Device confirmed completion. Dispatch does not prove execution. If confirmation is missing, check device status before retrying. Completion does not mean rewards have started.

[Understand this status](https://iotahome.site/en/machines)

## Sources and implementation

- [IOTA Watch agent implementation](https://github.com/molimao/iota/tree/main/scripts/device-agent)