Troubleshooting
What to check when the bot places no entries, shows a warning banner, says "Safe to stop: no", has its key rejected, reports a leverage or margin change, cannot reach Binance, runs without a take profit, skips coins, or reports clock errors. Most answers are already in the Activity log, in the bot's own words.
Why there are no entries
A confirmed wall has to pass many checks before an order goes out. Each check either passes quietly or writes one line saying why it stopped. So the fastest way to find the cause is to follow the funnel below and look for the matching line in the Activity panel (or in logs\wallbot.log / logs\wallbot_live.log).
1. The scanner
Only the top watch_count (5) coins that pass the scanner get live order-book tracking, so a coin that is not picked can never trade. Look at the Coins & scanner table's "Status" column; the reasons are listed in Scanner exclusions below. With symbol_allowlist set (the Trading instance presets XRPUSDT,DOGEUSDT), every other coin shows "excluded: not on the allowlist".
2. Wall confirmed
A wall must stand out from the book and stay for wall_persist_s (45 s). Then the log shows Support wall confirmed at 0.5401-0.5404 (0.42M USDT). No such lines means no walls big enough within 0.3% to 3% of price: thresholds (wall_k, wall_min_usd) or simply a quiet book. Many walls that are later "pulled" or "faded" before the bot can use them is also normal.
3. Pause, slots and guards
These are checked before any wall is looked at in detail. Some are silent:
| Cause | What you see |
|---|---|
| Entries paused (Pause entries, Prepare to stop, daily loss limit) | The banner: Paused (since ..., by you). Only Resume entries lifts it. or Entries paused. ...; the button reads "Resume entries" |
| Max open trades reached (pending entries count) | Nothing: the bot does not try. Compare the Trades panel with max_positions |
| This coin already has a trade on this side | Nothing (one trade per coin and side) |
| The other side of the coin has a trade | ... not used: the long side of XRPUSDT already has a pending trade and allow_both_sides is off |
| Movers cap | Entry skipped: movers slots full (1 open or pending movers trade(s)) |
| Live loss cap | A "TRADING STOPPED: loss cap reached" notification; the Live learning page shows "STOPPED" |
| Correlation guard | Entry skipped by the correlation guard: ... |
| Exchange not ready or rate limited | Entry skipped: user-data stream not connected and reconciled yet, or the 418 / 429 back-off; banner New entries waiting: ... |
Key guard engaged (testnet and live, after a -2015 or a burst of -1021) | Banner New entries waiting: API key / connection unstable (...): new entries paused until signed requests are clean for 10 min; see Entries paused by the key guard |
| A lost Wallbot order on the coin | Skipped wall: a lost Wallbot order on this symbol is being cancelled |
| Wall tried recently | Nothing: a wall is not tried again for wall_retry_cooldown_s (30 s) |
4. Wall notes: "not used: ..."
With log_unused_wall_reasons on, the otherwise silent cases get one line per wall and reason:
ENAUSDT support 0.23998-0.24011 not used: not the nearest wall (nearest 0.24388-0.24401), outside its stack span 1.5%
Only the nearest confirmed wall on a side anchors an entry. Walls within the stack span join its stack; walls beyond it are noted like this. A closer wall that appears while an entry is pending gets a similar line, for example SHORT XRPUSDT: closer wall 0.5412-0.5415 not used: reward/risk 0.80 below 1; keeping the pending entry at 0.5409.
5. Support/resistance level
With sr_filter on (default), the wall needs a 4h pivot level within the level tolerance: at or below price for support, at or above for resistance. The tolerance is sr_tolerance_pct (0.3%) with sr_tolerance_mode = fixed_pct (default). With atr each coin gets its own value from its volatility (sr_tol_atr_mult 0.1 × ATR(14), kept between sr_tol_min_pct 0.05% and sr_tol_max_pct 0.5%), and the log line shows that coin's value. This filter blocks many walls; it is the most common reason on a normal day.
Skipped wall: no 4h level at or below price within 0.3% of the wall at 0.5401-0.5404
Skipped wall: could not load 4h candles (...)
6. Safety checks
The coin must have nothing the bot did not create, and isolated margin must be confirmed:
Skipped wall: the account already holds a long position on this symbol that Wallbot is not managing
Skipped wall: the account has open orders on this symbol that Wallbot did not place
Skipped wall: the account has open conditional orders on this symbol that Wallbot did not place
Skipped wall: isolated margin not confirmed: ...
Close or cancel your own orders on that coin, or trade it on another account. Binance refuses to switch the margin type while orders (-4047) or a position (-4048) exist on the coin.
7. Plan rejected
The planner tries the highest leverage first and steps down. If no leverage passes, the log shows the reason of the highest one tried: Skipped wall at 0.5401: <reason>. Common reasons:
| Reason in the log | Meaning | What helps |
|---|---|---|
Price is already inside the entry zone (would chase) | Price is already at the entry; the bot only rests maker orders | Nothing; normal |
Position 3.74 USDT is below the exchange minimum; raise margin | Margin x leverage is under the coin's minimum notional | See Too-small positions |
Stop ... (fill ... after 5 bps slippage) is N ticks before liquidation ... at 75x; needs M | At the top leverage the stop sits too close to liquidation, and no lower leverage passed either | Rare; check liq_buffer_pct_of_margin and liq_min_ticks |
Round-trip fees would be 7.0% of margin at 100x (limit 5%) | Fees too high at the top leverage, and no lower leverage passed either | max_fee_pct_of_margin |
Position 52000 USDT falls in the 20x leverage bracket | The position is too big for the top leverage, and no lower leverage passed either | Usually rare; check the other lines for that wall |
Loss at the stop would be 64% of margin at 50x (limit 50%) | Wall-ticks stops only: loss above max_loss_pct | Use Wall % stops or a lower loss target |
Near-liquidation stop ... would sit in front of the wall's far edge ... | Near-liquidation stops only | Normal at high leverage on wide walls |
20x needed but Wallbot's long entry rests on this coin at 25x: the leverage is not changed under it | The coin's leverage is held while Wallbot has an order or position there | Wait until that order fills or is cancelled |
Binance allowed 50x instead of 75x: entry not placed; the next evaluation plans at 50x or less ... | The leverage check before the entry found Binance allows less than planned | Nothing; the next try plans at the allowed leverage. See Leverage changed outside Wallbot |
Binance refused 75x (it has 20x): entry not placed (...) / Could not read the coin's leverage on Binance (...): entry not placed | The leverage check before the entry could not set or read the coin's leverage | Usually clears on the next try; read the error in brackets |
no order book from binance yet, price-gap reasons | Feed still starting, or two-exchange mode gap checks | Wait; check the Feed status |
A plan that passes logs Wall hug at 75x (...): ..., including why the next higher leverage failed.
8. Reward/risk and flow filter
Skipped wall: reward/risk 0.80 below 1 (take profit 0.5462 before the wall at 0.5464-0.5467, stop 0.5372)
Skipped wall: flow filter: ...
The reward is the distance to the take profit in front of the nearest counter wall, minus fees; the risk is the distance to the stop. A setup without a counter wall is allowed and runs on stop and trailing only. The flow filter is off unless you set flow_filter.
9. Free-balance gate
Last, the exchange's free balance must cover the planned margin plus free_margin_buffer_pct (5%). Otherwise:
Skipped wall: not enough free balance: need 2.25, free 1.40 (pending entries hold 20.00, open positions 10.00)
The order is never shrunk to fit. If the exchange still refuses with -2019 (insufficient margin), the log says Binance rejected the entry for insufficient margin (-2019): skipped; the wall ... is not retried for 5 min. A worked example is in Worked examples.
Reading skip reasons
- Each reason is written once per wall, not on every book update. A new line appears only when the reason changes. So one line can explain an hour of silence.
- "Skipped wall: ..." lines come from the checks; "Skipped wall at <price>: ..." lines are plan rejections; "... not used: ..." lines are wall notes.
- The Live learning page (shown on the Trading instance, and in testnet and live) adds: "Entry sizing" (the last entries: available, own pending, cap, base, margin, free at the check), "Too small to trade" (skips per coin), "Coins at the current margin" (smallest position, max leverage, largest position, status) and "Binance errors".
python backtest.py livereport --data data_livewrites the same learning log as a report (item m lists setups skipped as too small). See Tools.
Tip. On the Trading instance, 0 fills is usually not a fault. Walls are touched rarely, and with 1 trade allowed, one pending entry blocks every other coin until it fills, times out (pending_timeout_s, 300 s) or is cancelled.
The foreign-margin banner
The bot compares the account balance with the available balance and the margin of its own trades. Anything left over is "foreign": margin used by positions or orders it did not open. When that exceeds the larger of foreign_margin_warn_usdt (1 USDT) and foreign_margin_warn_pct (1% of the balance), the banner shows:
12.34 USDT of margin is in use by positions or orders Wallbot did not open; new entries are sized from 26.00 USDT (available 20.00 + Wallbot's own pending entries 6.00).
The second half is the actual sizing base (foreign_banner_sizing_base), so you can see how big the next entry will be.
Common causes
- Manual positions or orders on the same futures account. They are yours and are never touched. The bot also skips any coin where you have a position or open orders (see stage 6 above). A separate sub-account for the bot avoids this.
- Lost Wallbot orders. An order with the bot's
wbclient-id prefix that no trade tracks. Withlost_orders_not_foreignon it is reported separately, not as foreign:3.10 USDT of margin is held by lost Wallbot order(s) on ETHUSDT; they are being cancelled (not foreign).The reconciliation cancels it, and new entries on that coin wait. - A leverage change under a resting order. Binance re-margins a resting order or an open position at the new leverage, which used to show up as foreign margin. With
leverage_hold_while_restingon (default), the leverage is now never changed while Wallbot has an order or position on the coin. A plan that would need another leverage is skipped with the reason, and a re-plan sets the new leverage only after the old entry's cancel is confirmed.
To check: open Binance Futures, look at open orders, conditional orders and positions, and find anything without the wb prefix. If the banner stays after you closed your own trades, wait for the next reconciliation pass (every 60 s).
"Safe to stop" says no
The top bar's "Safe to stop" turns "yes" only when stopping the process cannot leave an order behind. Hover over it to see the reason. Paper mode is always "yes" (paper mode: no orders on an exchange).
| Reason shown | What to do |
|---|---|
new entries are not paused: press Prepare to stop | Press "Prepare to stop" (or "Pause entries") |
N order action(s) in progress | Wait a few seconds; placements, cancels and stop moves are finishing |
resting entry order(s) on XRPUSDT | "Prepare to stop" cancels them and waits for each confirmation |
a stop is being moved on XRPUSDT | Wait; a new stop is confirmed before the old one is cancelled |
open position(s) without a confirmed exchange stop: XRPUSDT | Do not stop. Check the position on Binance; the bot is placing or retrying its stop |
unconfirmed entry cancel(s): XRPUSDT order 123... | The cancel is retried until Binance confirms it; you can check the order on Binance |
When it is safe, the hover text reads like entries paused, no resting entries, 1 open position(s) with their exchange stops. Open positions are fine: they keep their stops on the exchange.
Warning. On an instance in live mode, never stop the process while it says "no". A database with no open or pending trades is not enough: an entry can be on its way to the exchange before it is saved. If "Prepare to stop" cannot finish, the log says NOT SAFE TO STOP: ... and a high-priority "NOT SAFE TO STOP" notification lists the reason. See Prepare to stop.
Key rejected (-2015) and the IP whitelist
Binance answers -2015 when the key is wrong, lacks futures permission, or the request comes from an IP that is not on the key's allow-list. The most common cause is a home internet IP that changed.
In testnet and live
While rejections last, the banner shows:
Binance is rejecting the live API key (-2015: invalid key, IP or permissions): 3 rejection(s) in the last minute, request IP 203.0.113.7. Add the IP to the key's allow-list on Binance.
After key_rejected_threshold (3) rejections within 60 s, a high-priority "BINANCE KEY REJECTED (-2015)" notification lists the request IPs Binance reported, at most once per key_rejected_alert_min (15 minutes). An IP never seen in a rejection before is reported at once, with "NEW IP ... Add it to the key's IP allow-list." While this lasts, orders, cancels and position checks can fail at random, and live mode does not fall back to anything.
- Open Binance → API Management → the key → Edit restrictions.
- Add the IP from the notification (or banner) to the trusted IPs. Keep withdrawals disabled.
- Press "Test connection" in Settings → Account & keys. The rejection banner clears by itself about 2 minutes after the last rejection. New entries stay paused by the key guard (below) until signed requests have been clean for 10 minutes.
Entries paused by the key guard
With key_unstable_guard on (default), the first -2015, or key_unstable_1021_burst (3) clock rejections within a minute, pause new entries. You get one high-priority notification, "ENTRIES PAUSED: API KEY UNSTABLE (IP ...)", and the banner reads:
API key / connection unstable since 19:32:05 (...; IPs 203.0.113.7): new entries paused until signed requests are clean for 10 min.
- Every resting entry is cancelled at the first request that gets through (log:
Key guard: 1 resting entry cancelled at the first request that got through). Stops are never cancelled. - While it lasts and a position is open, its stop on Binance is checked every 15 s. If Binance does not answer, you get "CANNOT CONFIRM STOPS (key unstable)": check that position on Binance yourself.
- New entries go again once signed requests have been clean for
key_stable_minutes(10 minutes). Then "ENTRIES RESUMED: API KEY STABLE" lists the IPs Binance reported. You do not need to press anything.
In paper mode (the Research instance)
Paper mode reads brackets and fees with the saved key, read-only. If it is rejected, paper trading continues on the brackets and fee rates cached while the key worked (or assumed values), retries every key_retry_s (10 minutes) and switches back by itself. The banner reads Binance key rejected (IP 203.0.113.7): using cached brackets, oldest cache 3.2 h. Retrying every 10 min. See IP whitelist.
Leverage changed outside Wallbot
A "LEVERAGE CHANGED coin: Ax -> Bx" notification means the coin's leverage on Binance is no longer the leverage Wallbot last set there. Wallbot did not request that change. The log reads Leverage on XRPUSDT changed outside Wallbot: 75x → 20x.
The most likely cause is the Binance app's default-leverage setting on the futures screen, which can overwrite the per-coin leverage Wallbot sets. Other causes are a change in the app, on the website or through another API key.
- Turn the default-leverage setting off in the Binance app.
- Do not change leverage in the Binance app on coins Wallbot trades while it runs. Trade other coins manually instead.
What Wallbot does about it (verify_leverage_before_entry, on):
- It reads the coin's real leverage before every entry, re-place and re-plan, and sets the planned leverage again (log:
Leverage re-set to 75x (Binance had 20x)). - It never does that under its own resting order or open position. The entry is then not placed, with the reason
leverage on Binance is 20x, the plan needs 75x, and Wallbot's long entry is on this coin: the leverage is not changed under it. - If Binance allows less than planned, the entry is not placed and the next evaluation plans at the allowed leverage, with margin, liquidation and every check recomputed.
- The notification is sent at most once per coin per hour. The coin's maximum leverage is also re-read every
leverage_bracket_refresh_min(60 minutes) and at once after a mismatch. A changed maximum sends "MAX LEVERAGE coin: Ax -> Bx".
Reserved margin above plan
In testnet and live, every margin_check_interval_s (60 s) while Wallbot has orders or positions, it compares the margin Binance reserves for them on each coin with the margin it planned. When Binance reserves more than margin_reserve_alert_pct (20%) above plan, you get a high-priority "MARGIN coin: x reserved vs y planned" alert, at most once per coin per hour. The body gives the leverage on Binance and the planned leverage, and ends with "Nothing was cancelled or closed."
The usual cause is a leverage change on the coin, which makes Binance re-margin the resting order or open position. If the leverage on Binance differs from the plan, you also get "LEVERAGE CHANGED" (see above). Check the coin on Binance. The position keeps its stop; Wallbot does not cancel or close anything because of this alert. Set the setting to 0 to switch the alert off.
Binance cannot be reached (blocked or intercepted connection)
Some networks block Binance or answer in its place, for example with a DNS block page or a certificate that is not Binance's. Wallbot does not try to get around that. It reports what failed:
- At start, when the coin list cannot be loaded, the engine stops and the banner reads
Engine stopped: Could not reach Binance market data (...). Check the server's internet access and that Binance is available from its location.The brackets name the error, for example a connection, timeout or certificate error. A critical notification starting "CRITICAL Engine failed to start" goes out as well. With MEXC the text isCould not reach MEXC (...). - When the market-data stream drops while running, the "Feed" box reads
reconnecting (...)with the error type, and the bot retries every few seconds. MEXC showsretrying (...).
Run the bot on a network or server where Binance is available. Open positions keep their stops on the exchange while the bot cannot reach it.
A trade has no take profit
The take profit sits tp_ticks (2) in front of the nearest confirmed counter wall: a resistance wall above a long, a support wall below a short, within wall_max_dist_pct (3%) of price. Without such a wall there is no target, and the trade runs on its stop and trailing stop. You will see one of these:
No counter wall at the fill: the trade runs on stop and trailing stop
Take profit 0.5462 removed (counter wall 0.5464-0.5467 pulled, none further); the trade runs on stop and trailing stop
With tp_reacquire on (default), the trade picks up a target as soon as a counter wall confirms, checked on every confirmation and every 5 s, even while entries are paused. The target must lie beyond both the current price and the fill price:
Take profit tracking restarted (counter wall 0.5470-0.5473 confirmed): 0.5468, before the counter wall at 0.547-0.5473
Other things that look like a missing take profit:
- Not on the exchange yet. The target is tracked locally and the order is placed only within
tp_arm_distance_pct(0.3%). If price jumps past it first, the bot closes at market:Price ... reached the take profit ... before it was armed: closing at market. - After a restart. An old take-profit order is cancelled (
tp_restart_cleanup) and a new target is re-acquired from the live book. - Pending entries. Nothing is tracked or armed before the fill.
- Settings.
tp_modeisoff, or the entry model is loss budget (take profits work with wall hug only).
Scanner exclusions
The Coins & scanner table's "Status" column gives the reason for each coin that was not picked. Coins below scan_min_volume_usd (50M USDT) are not listed at all, and only the top scan_max_candidates (40) by volume are analysed.
| Status text | Rule |
|---|---|
excluded: on the denylist | symbol_denylist |
excluded: non-ASCII symbol | exclude_non_ascii_symbols |
excluded: listed 12 days ago (minimum 30) | min_listing_age_days |
excluded: max leverage 10x (minimum 20x) | min_max_leverage (needs the bracket table: an API key on Binance) |
excluded: not on the allowlist | symbol_allowlist |
filtered: spread 7.5 bps (max 5) | max_spread_bps |
filtered: tick 0.0400% of price (max 0.02%) | max_tick_pct |
filtered: depth within 1% 0.80M USDT (min 1M) | min_depth_1pct_usd |
filtered: 15m ATR 0.12% is 0.07x the wall band middle 1.65% (min 0.1x) | min_atr_to_wall_band |
filtered: spoof rate 64% of confirmed walls pulled (max 50%) | max_spoof_rate |
filtered: smallest position $70.00 > limit $15 | max_smallest_position_usdt |
filtered: smallest position $70.00 > affordable $20.00 (10% of $10.00 x 20x) | affordability_filter |
not enough candles | Too little history for the indicators |
trending (ADX 31) | scan_max_adx (25) |
volatility squeeze (12 pctile) | scan_min_bb_pctile (20) |
funding +0.080% | scan_max_funding_pct (0.05%) |
Passed coins may show near a 4h level (+10) (a score boost, never an exclusion), and movers show mover: +12.40% in 24h; core filter: trending (ADX 40). The "excluded" rules are checked first, without fetching candles. Each scan also logs its exclusions once.
Too-small positions
Each coin has a smallest position the exchange accepts: the largest of the minimum notional, one quantity step x price, and the minimum quantity x price. The bot's position is margin x leverage, and the quantity is always rounded down to the step. So with a small balance, some coins can never be traded.
Example
Illustrative numbers. The Trading instance has 10 USDT available and margin 10%: 1.00 USDT per entry. On a coin with a maximum of 20x, the largest position is 1.00 x 20 = 20 USDT. A coin whose smallest position is 70 USDT cannot be traded at all. A coin with a 5 USDT minimum can.
- Without filters, such a coin is still scanned and watched, and each wall is skipped at the plan:
Skipped wall at ...: Position 3.74 USDT is below the exchange minimum; raise margin. The Live learning page counts these under "Too small to trade". affordability_filter(preset on for the Trading instance) drops these coins at the scanner instead, recomputed every scan, so coins drop out as the balance shrinks.max_smallest_position_usdtdrops coins whose smallest position is above a fixed USDT amount.- The Live learning page's "Coins at the current margin" table shows each coin's smallest position, maximum leverage, largest affordable position and whether it is allowed.
Warning. Raising margin_pct to make small coins tradeable also makes every trade's possible loss bigger. In live mode it needs a typed I ACCEPT.
Clock errors (-1021)
Every signed Binance request carries a timestamp and a 5,000 ms receive window. If the PC clock is off by more than that, Binance rejects the request with -1021 ("timestamp outside recvWindow"). Such a request was never executed, so retrying it is safe.
- With
clock_resync_on_1021on, the bot resyncs with Binance's server time and retries that request once. The log showsPOST /fapi/v1/order: -1021 (timestamp outside recvWindow); clock resynced (offset +2350 ms), retrying onceandClock offset vs Binance: +2350 ms (was +12 ms; -1021 sync). - It also resyncs every
clock_resync_min(10 minutes) and logs the offset. - The "Clock vs Binance" box in the top bar (testnet and live) shows the current offset. It turns red above 1,000 ms. Hover for the last sync time and the number of resyncs after -1021.
In testnet and live, key_unstable_1021_burst (3) -1021 rejections within a minute engage the key guard, which pauses new entries for at least 10 minutes.
Occasional -1021 lines after the PC wakes from sleep are harmless. Frequent ones mean the Windows clock drifts: open Windows Settings → Time & language → Date & time and press "Sync now", and keep "Set time automatically" on.
Related
- Worked examples: the numbers behind plans, stacks, breakeven and sizing.
- Dashboard: Activity and Live learning.
- Reconciliation: how lost orders and positions are found.
- Tools:
livereport,liq_calc.pyand the testnet check.