My bot went offline
Offline usually means Steam dropped the connection, not that something is broken. Most of the time the bot fixes it before you finish reading this.
What happens on its own
Steam disconnects clients routinely — maintenance, a busy region, a network hiccup. When it happens, the bot notices and reconnects by itself, then resumes the exact game and queue it was on. You will see it flip back to running without touching anything.
So the first thing to do is nothing, for a minute or two.
When it needs you
A bot stays offline only when it cannot get back in on its own. There are three causes, and the Dashboard tells you which one it is.
It is waiting for a Steam Guard code
The most common. Steam asked for a code on the new sign-in. Enter it on the Dashboard and the bot continues. Setting a shared secret stops this from happening again — see Steam Guard and 2FA.
The password no longer works
Shown as needing re-authentication. Nearly always because the account's password was changed somewhere else. Open the bot's settings, update the password, press start.
Your package expired
When access runs out, bots are stopped deliberately — this is not a fault. Renewing brings them straight back, with games and settings intact. See Subscription and renewal.
If you sign into the same Steam account yourself and launch a game, Steam kicks the bot off — two sessions cannot play at once. The bot will keep trying to reconnect, and the two of you will take turns kicking each other. Pause the bot while you play, or farm on a separate account.
Getting told about it
You do not have to watch the Dashboard. On Growth and Scale packages, EasySteamFarm can notify you the moment a bot goes offline, needs a code, or finishes farming — in the panel, by e-mail, or to a Discord webhook. Turn the ones you want on under Settings → Notifications.