Docs·Web App·Auto Trade

Toasts & status feedback

How Auto Trade surfaces every engine event in real time. Toast types, the OFFLINE / CONNECTING / SIGNAL LIVE status pill, sticky vs auto-dismiss behaviour, and the global mute for high-frequency Full-Auto sessions.

The Auto Trade toast stack surfaces every engine event in real time — signal received, order placed, fill, TP hit, SL moved, error. Toasts pop in the bottom-right of the screen across every page (not just Auto Trade tabs), so you can leave the app on the Chart Terminal and still see what the engine is doing. Each toast type has a distinct colour and behaviour (some auto-dismiss after a few seconds, some are sticky until you click them). Above the chart, three connection chips give you the at-a-glance status of the live signal feed, the Binance API connection, and the engine itself.

The three status chips on the top bar

Above every Auto Trade tab, three chips show the live health of the engine. All three must be green before LIVE means anything:

ChipGreenYellow / amberRed
SIGNAL LIVESignal hub is connected and signals are streaming.CONNECTING — first connect or reconnect in progress. Brief; if it stays here for more than 10s, investigate.OFFLINE — signal hub is unreachable. No new signals will arrive until this clears. Open positions continue to run with the orders already on Binance.
API ConnectedBinance API is reachable; recent calls succeeded.Throttled / rate-limited — calls succeeding but slow.API down or API key invalid — orders cannot be placed or amended.
Auto-TradeEngine is armed (LIVE on, plan active, prerequisites met).Some prerequisite is partially met — view the banner for details.LIVE off, plan expired, or position mode mismatch.

A red chip on SIGNAL LIVE does not stop existing TP/SL orders from filling on Binance — those orders live on the exchange. It does mean the engine will not see new signals or apply trailing-SL amends until the connection recovers.

Practical: if SIGNAL LIVE goes red while you have Full-Auto trades running, do not assume the engine will move SL after the next TP fills. Check Running Positions and consider moving SLs manually until the chip recovers.

Toast types

TypeColourStickyExample message
Signal receivedNeutralNo (3s)Crypto USD-M · ETHUSDT LONG @ 3245.20
Order placedAmberNo (4s)ETHUSDT LIMIT BUY 0.05 @ 3242.10 → working
FillBull green / Bear redNo (4s)ETHUSDT LONG entry filled 0.05 @ 3243.00
TP fillBull greenNo (4s)ETHUSDT TP2 filled 20% @ 3275.00 — +$15.20
SL moved (trailing)AmberNo (3s)ETHUSDT SL moved → 3243.00 (breakeven after TP2)
SL hitBear redYesETHUSDT SL hit @ 3210.00 — −$18.75
Final closeNeutralNo (5s)ETHUSDT closed — realized +$42.10
Engine errorBear redYesOrder rejected: MARGIN_NOT_SUFFICIENT
Signal skippedGreyNo (2s)ETHUSDT skipped — leverage 100× outside range
DisconnectAmberYesSignal hub disconnected — retrying in 3s
ReconnectBull greenNo (2s)Signal hub reconnected

Sticky vs. auto-dismiss

BehaviourWhy
Auto-dismissInformational events you can miss without consequence — fills, signals received, TP hits, SL moves. They're logged in History anyway.
StickyEvents that need your attention — SL hits (your money just took a haircut), Binance rejections (something needs fixing), disconnects (engine is effectively paused until reconnect). Click to dismiss.

Click-to-jump

Click any toast to jump to the relevant tab:

  • Signal received / fill / TP / SL toasts → Running Positions with that row scrolled into view.
  • Final close → History with that trade's detail dialog open.
  • Engine error → the affected tab with the error highlighted.

Mute / unmute

The top-right of the toast stack has a small speaker icon:

  • Unmuted (default) — every toast appears.
  • Muted — only sticky toasts (SL hits, errors, disconnects) appear; informational toasts are suppressed.

Useful when the engine is firing many trades and you want to focus on the chart without constant pop-ups. Sticky alerts always come through regardless of mute state.

Sound

Off by default. Enable from the Auto Trade cog menu → Sound on toast type X per type. Common preset:

  • SL hit + engine error + disconnect → ON.
  • Everything else → OFF.

Where toasts are NOT enough

Toasts are ephemeral; for a permanent record use:

Common pitfalls

  • Missed an SL hit toast. Sticky toasts wait for a click — but a page reload clears them. Always check History or Positions after a reload.
  • Sound never plays. Browser autoplay policy — you have to interact with the page first before sound is allowed.
  • Toast spam during Full-Auto on multiple symbols. Mute informational toasts (see mute above) and rely on the Signal Live Monitor / Running Positions tabs instead.
  • Ignoring an OFFLINE status pill. While red, no new signals arrive and trailing-SL amends are queued. Investigate before assuming Full-Auto is doing anything.

What's next