Daily operation
How to pause and resume the bot, how to stop it without leaving orders behind, how to update it safely, and what to look at each day.
Pause and resume entries
"Pause entries" in the top bar stops the bot from opening anything new. At the same time it cancels every pending entry order. Open positions are not touched: they keep their exchange stops, take profits and trailing. The button then reads "Resume entries".
A manual pause survives restarts (persist_manual_pause, on by default). This covers "Pause entries", "Prepare to stop" and "Close all". After a restart the bot:
- starts with entries paused, before any market feed or entry logic runs;
- shows "Paused (since <time>, by you). Only Resume entries lifts it." in the banner;
- sends a "STARTED PAUSED" notification.
On a Linux VPS, an unplanned server restart also starts the Trading instance paused, even if you had not paused it (reboot_start_paused). You get a high-priority "VPS rebooted — Wallbot started paused, check positions" notification. Check the open positions and their stops on Binance and on the dashboard, then press "Resume entries".
Only the "Resume entries" button lifts a manual pause. The bot never resumes by itself after you paused it.
Note. The daily loss limit pause works differently. It is set by the bot, not by you. It is not kept across restarts, and it lifts at the next UTC day, when you press "Resume entries", or when you press "Reset today's loss count" on the Live learning page (in live mode you type I ACCEPT to confirm). A manual pause stays after a reset. See Loss caps.
Prepare to stop
Stopping a bot that trades on an exchange is not the same as closing a program. An entry order can be on its way to the exchange at the moment you press Ctrl+C, and the bot would no longer be there to watch it. "Prepare to stop" removes that risk. In testnet and live it does this, in order:
- No new entries are opened. This counts as a manual pause.
- It waits for every order action in progress to finish: entry placements, cancels, stop placements and moves, take profits, closes and margin top-ups. It waits up to
safe_stop_timeout_s(30 s). An entry that fills meanwhile gets its stop first. - Every resting entry order is cancelled, and each cancel must be confirmed by the exchange. A failed cancel is tried again.
- Open positions are left as they are, with their exchange-side stops. Stops are never cancelled by this step.
A toast then says "Safe to stop: ..." or "NOT safe to stop: ...". The same steps run automatically on every shutdown in testnet and live (safe_shutdown). Exchange errors never abort them: they always finish with an honest Safe or NOT SAFE.
Safe to stop: yes or no
The "Safe to stop" box in the top bar answers one question: can you stop the process right now without leaving anything unwatched on the exchange? "yes" needs all of these:
- entries are paused ("Prepare to stop" or "Pause entries");
- no order action is in progress;
- no resting entry orders and no unconfirmed cancels;
- every open position has a stop the exchange has confirmed, and no stop is being moved.
Paper mode always shows "yes", because nothing rests on an exchange.
"no" tells you why when you hover over it. The reasons the bot gives are:
| Reason shown | What to do |
|---|---|
| "new entries are not paused: press Prepare to stop" | Press "Prepare to stop". |
| "N order action(s) in progress" | Wait a few seconds; it normally clears on its own. |
| "resting entry order(s) on ..." | Prepare to stop cancels them. If it stays, the cancel is not confirmed yet. |
| "a stop is being moved on ..." | Wait: a stop move places the new stop before cancelling the old one. |
| "open position(s) without a confirmed exchange stop: ..." | Do not stop. Check that position on the exchange now. |
| "unconfirmed entry cancel(s): ..." | The bot keeps retrying. Check the exchange's open orders. |
Warning. "Safe to stop: NO" means something might be left on the exchange without the bot watching it. Do not stop the Trading instance until it says "yes". If it cannot get there, the bot sends a "NOT SAFE TO STOP" notification; check open orders, positions and stops on the exchange yourself.
"Resume entries" undoes "Prepare to stop" if you change your mind.
Updating Wallbot (the deploy procedure)
Both instances run from the same folder, so an update always means restarting both. Follow these steps every time, especially while the Trading instance is in live mode:
- Prepare. On the Trading dashboard (8788), press "Prepare to stop".
- Wait for "Safe to stop: yes". A quiet moment or an empty trade list is not enough: an entry can be on its way to the exchange before it is saved.
- Stop both instances cleanly with Ctrl+C in each launcher window. Each one runs the safe shutdown and its launcher keeps logging until the bot has exited.
- Back up both databases in place, for example:
copy data\wallbot.db data\wallbot.db.pre_update_20261001_0900.bak copy data_live\wallbot.db data_live\wallbot.db.pre_update_20261001_0900.bak - Update the files.
- Restart both with
start_wallbot.batandstart_wallbot_live.bat. - Confirm on the Trading instance, in its Activity log or
logs\wallbot_live.log:- every open position was reconciled:
Resumed open long with stop at ...; - each position has its stop re-armed;
- no unconfirmed cancels remain;
- it started paused ("STARTED PAUSED" notification and the "Paused ... by you" banner).
- every open position was reconciled:
- When you are ready, press "Resume entries".
Open both dashboards after a restart to make sure each page loads. A page that reconnects and shows data is working.
On a Linux VPS
On a VPS the instances run under wallbot.sh (see Getting started). Run these commands in the Wallbot code folder:
- Prepare. Press "Prepare to stop" on the Trading dashboard (through the SSH tunnel). When you are away from a browser,
./wallbot.sh stop liveruns the same safe shutdown: entries paused, order actions finished, resting entries cancelled and each cancel confirmed, open positions keep their exchange stops. - Stop only when it is safe. Wait for "Safe to stop: yes" on the dashboard, then run
./wallbot.sh stop live. Without the dashboard, check that the shutdown logged "Safe to stop" (./wallbot.sh stopprints the last log lines). If it logged "SHUTTING DOWN WHILE NOT SAFE", check open orders, positions and stops on Binance at once. - Back up the databases in each data folder, for example:
cp /wallbot/data_live/wallbot.db /wallbot/data_live/wallbot.db.pre_update_20261001_0900.bak cp /wallbot/data/wallbot.db /wallbot/data/wallbot.db.pre_update_20261001_0900.bak - Copy the new code into the code folder.
- Start with
./wallbot.sh start live(and./wallbot.sh start research), then confirm the same points as in step 7 above.
Warning. A plain shutdown does not keep a pause. The safe shutdown pauses entries only while the bot stops. After ./wallbot.sh start live the bot trades at once, unless a pause was saved before: "Pause entries" or "Prepare to stop" on the dashboard.
The disk guard keeps only the newest 2 backups (*.db.*.bak) per database (disk_backups_keep) and deletes older ones. Copy a backup elsewhere if you want to keep it longer.
Viewing the dashboards remotely (SSH tunnel)
The dashboards listen on 127.0.0.1 only, so they cannot be reached from the internet. To see them from another device, forward the ports through SSH. Use your own server address in place of you@your-server.
- From a PC: run
then openssh -L 8788:127.0.0.1:8788 -L 8787:127.0.0.1:8787 you@your-serverhttp://127.0.0.1:8788(Trading) andhttp://127.0.0.1:8787(Research) in your browser. The dashboards work as long as that SSH session stays open. - From a phone: use an SSH app that supports local port forwarding. Add the same two forwards (local port 8788 to
127.0.0.1:8788, local port 8787 to127.0.0.1:8787), connect, then openhttp://127.0.0.1:8788in the phone's browser.
Warning. Do not change the dashboards to listen on a public address. The SSH tunnel is the only way in.
Reconciliation every minute
In testnet and live, the bot compares the exchange with its own records every reconcile_interval_s (60 s), soon after any exchange error, and after every reconnect. It looks at open orders, stop (algo) orders and positions:
- A Wallbot order (client id starting with
wb) that no trade tracks is cancelled. Orders younger than 15 s are left alone. - A real position whose trade is still marked pending (a missed fill) is taken over with its stop.
- A position from a Wallbot order that no trade tracks is adopted with its planned stop if that stop is still valid, or closed at market. You are notified either way.
- A position without a confirmed stop on the exchange raises an "UNPROTECTED POSITION" alert and a dashboard warning.
- Orders and positions without the
wbprefix are yours and are never touched.
More detail is in Safety rules.
What to check each day
A few minutes a day keeps surprises small:
- Top bar. "Feed" reads "streaming". "Clock vs Binance" is not red. No unexpected banner.
- Mode pill. Each instance is in the mode you expect.
- Trade cards. Every open trade shows a sensible state. A trade that stays "Waiting for fill" for a long time, or a card you did not expect, deserves a look.
- Activity log. Scroll for red (critical) lines and read them.
- Notifications. Read the daily summary: trades, P&L, cancelled entries, restarts and critical events. More than 0 restarts means the launcher restarted the bot; find out why in the log.
- Exchange app. Compare the bot's open positions and orders with what the exchange shows. Each bot position should have its stop.
- Live learning page (Trading). Loss caps not reached, "Trailing: longest window without a stop" at 0 ms, and no new Binance error codes you do not understand.
- Disk. On Research with recording on, check the "Recording" box and move or delete old days. On a VPS the disk guard prunes the oldest recording days by itself; watch the "Disk" box in the top bar and act on a disk notification.
Tip. If anything looks wrong and you are unsure, press "Pause entries". It costs nothing: open positions keep their stops, and you can resume when you understand what happened.