The Overview dashboard
The screen the app opens on, and a quick read on how the fleet is doing right now.
What's on it
Total accounts — how many you have, and how many are enabled. A disabled account is kept but never run.
Accounts done — how many have finished a full lap of their action list in the current run. Before you press Start it reads "Waiting to start".
Bot uptime — how long the current run has been going. The timer starts with the bot and stops when you stop it. If every tab is resting between cycles the clock is held, rather than counting rest as uptime.
Resource overview — your food, wood, stone and gold added up across every account the bot has read.
Recent activity — the last few things the bot did, in plain language, from the current run. The Logs button beside it opens the full feed.
Run summary — successful actions, warnings and errors for this session. It resets when you start a new run, not daily.
"From N accounts" is the important bit
The corner of the resource overview says how many accounts the total came from, and that number matters more than the total does.
An account the bot has never booted has no reading, so it contributes nothing — which makes the total smaller than you'd expect. That's exactly why the count is shown rather than hidden. Readings are taken while an account is running, so the numbers fill in as the fleet laps.
See account snapshots for where each figure comes from.
Troubleshooting
It says "from 2 accounts" and I have twenty. Only two have been booted and read so far. Give it a lap.
An account's resources look out of date. They're from the last time that account ran. Nothing polls an account that isn't running.
Uptime says Stopped. The bot isn't running. Press Start.
The feed says "Waiting for runtime events". The bot hasn't started, or has only just started and nothing has happened yet.
Errors isn't zero. Open Logs and read the feed. An error is a step the bot couldn't complete; it usually recovers on its own, and the count is a tally for the session rather than a list of things still broken.
Accounts done stays at zero for ages. A full lap takes a while, especially the first time when instances have to boot. Watch the activity feed instead — it moves continuously.