Train at Home registration states: from queued to training

You start Train at Home and, hours later, it still is not training. Maybe your menu bar says confirmed and you wonder what it is waiting for. This guide lists the phases a miner goes through between joining the queue and training, what each one looks like in subnera, and what to do at each step. The answer is usually to wait.

subnera is unofficial and not affiliated with IOTA, Macrocosmos or Bittensor. It only reads the official app's CLI log and shows what it finds. It cannot move you through any of these phases faster.

Why you need this

The official window freezes on its last step, usually "Running speedtest...", because the request that would report your queue position fails. Why the app looks frozen explains that. The real progress is written to the CLI log, and subnera turns it into a phase, a dot colour and a headline.

The phases in order

Phase (card)	Menu bar headline	Dot	What it means
Starting	…	yellow	The official app is launching the miner.
Speed test	…	yellow	The miner is running its speed test.
Queued	position, such as 1564 ▼	yellow	Waiting in the admission queue.
Registering	confirming, confirmed or succeeded	yellow	Past the queue, going through the later registration steps.
Training	L1 · 358k tok/h	green	A layer is assigned and training lines are in the log.

These can also appear:

Phase (card)	Menu bar headline	Dot	What it means
Idle	idle	blue	Assigned, but waiting for work to arrive.
Resetting	…	yellow	The miner is restarting.
Off	off	red	The log has been silent for more than 2 minutes, or the official app is stopped.
Unknown	? or a raw status word	grey	A state the parser does not recognise.

The card in the open menu uses plainer wording than the headline. For example, confirmed appears there as "confirmed — waiting for a layer slot".

Queued

While you are queued, the log carries a numeric 'position' and 'status': 'queued'. The menu bar shows the position with a trend arrow, and the menu adds a rate and a rough ETA. How long this takes depends on the queue and varies a lot. The details, including the arrows, are in the queue position guide.

What to do: nothing. Do not restart the official app. A restart while queued sends a new registration request and puts you back at the end of the queue.

Confirming

Once you reach the front, the position disappears: later responses carry 'position': None, which is normal and not an error. The status becomes confirming. The menu describes it as "front reached — attesting". This is an attestation step.

What to do: nothing. A rare processing status can show up around this point. subnera treats it as a registration step too and displays the raw word.

Confirmed: waiting for a layer slot

This is the phase behind most "confirmed but not training" searches. confirmed means your registration went through, but no layer slot is free for you yet. This step can last hours. It does not mean something is broken, and nothing on your side speeds it up.

What to do: leave the app running and keep the Mac awake (see keeping a Mac awake). Restarting is not recommended: the project has seen one case where a restart during confirmed kept the same queue id and status, but one observation is not a guarantee, so the safe default is not to restart.

Succeeded: assigned

succeeded means you have been assigned a layer. The menu says "assigned — loading the model". The miner then downloads and prepares what it needs, and training lines begin to appear in the log. How long that takes varies.

Training

When the log shows real training lines, the phase becomes Training. The dot turns green and the headline reads like L1 · 358k tok/h, a layer number and a token rate. The rate shows … for a while until enough passes have been seen to measure it. If you do not see a rate yet, give it a few minutes. The parser recognises these training lines:

FORWARD complete
BACKWARD complete
Optimization step #<n>

See reading training stats for what the numbers mean.

Idle: assigned but waiting

idle (blue) is not the same as queued. The miner has a layer but receives no activations yet, and subnera only reports it when the log shows an empty queue and no incoming work, repeatedly and recently. It is a waiting state, not a fault.

Off, and when to act

off appears when the log has been silent for more than 2 minutes, or when the official app is not running. It is the one state that may need action. First check that the official app is open. If it is running but the log stays silent for several minutes, see the troubleshooting guide. subnera also has an opt-in auto-restart option for a crashed app, covered in the watchdog guide.

A grey ? or an unrecognised word means the log has a shape the parser does not know. It never stops the app. It is useful information if the official app has been updated.

How long should it take?

There is no fixed figure. The queue wait varies with how many miners are ahead of you, and the confirmed wait can last hours. Compare the current state with the one you saw an hour ago rather than looking for a deadline.

Checklist

1. Read the headline and the dot colour, not the official window.
2. Queued, confirming, confirmed and succeeded are all normal steps. Do nothing.
3. Do not restart the app before you are training, least of all while queued.
4. Green with a layer and a rate means you are training.
5. Red off is the only state that usually needs a look. Start with the troubleshooting guide.
6. If you need subnera first, see how to install it.