Reading the BotDaddy activity log

Everything the bot has done this run, in plain language, with filters. The most useful thing on this screen is knowing which lines are normal — because a lot of alarming-looking ones are.

Four counters across the top — Total, Success, Warnings, Errors — for the current run. Below them a search box, a level filter, and an account picker that narrows the feed to one account.

What the levels mean

Info — ordinary progress. Booting an instance, opening a screen, moving to the next action.

Success — something finished. An action completed, a march went out, a reward was claimed.

Warning — something didn't go to plan but the bot handled it. An action retried, a screen re-found, a board that ran out of time. Warnings are normal in small numbers.

Error — something the bot couldn't complete even after retrying. It will usually have restarted the game or the instance to recover. A handful across a long run is normal.

Common lines, and what they're really saying

"Relaunching the game" — the bot couldn't get to a screen it recognised, so it's restarting the game rather than pushing on from an unknown state. It picks up where it left off.

"Restarting instance" — the same idea one level up. The emulator itself is being restarted, usually because restarting the game alone didn't fix it.

"…didn't complete, restarting instance to retry" — one action failed its own retries, so the account gets one instance restart and the action is tried once more.

"…still failed after restart — moving on" — that second attempt failed too. The action is given up on for this cycle and the next one runs. The account is not parked for this.

Account parked or failed — the bot has stopped running that account because something only you can fix: missing credentials, a game version it can't use, a wrong IGG ID. The line says which.

Troubleshooting

Lots of warnings. Normal in small numbers — the bot retries constantly and reports what it retried. Worth a look if one account or one action produces most of them.

The same account keeps erroring. Filter the feed to that account. Usually it's that account's game state rather than the bot: an unfinished tutorial step, a modal the game won't dismiss, or a building an action needs that isn't built yet.

I restarted the bot and the feed emptied. The counters and feed are for the current run and start fresh each time.

It says "No logs found". Either the bot hasn't started, or your filters exclude everything. Reset the level filter to All and clear the search.

I need more detail than the feed gives. Full logs are written to Documents\BotDaddy. That's what to send with a support request.