Troubleshooting#
When something looks wrong, the Notifications screen is the first place to check — webhook errors, trade failures, and rejected alerts all surface there. Webhook payloads that are ignored (duplicates, stale, signals while no trade is open) are recorded silently in the strategy's webhook log instead.
Articles:
- Binance error codes — what each code means and how to fix it.
- Rejected trades — the full list of HookTrader-side rejection reasons.
- Dashboard disconnects — why the dashboard goes "disconnected" and what's safe to ignore.
- Open-trade state loss — the recovery path when open-trade state is lost mid-trade.
Quick triage#
| Symptom | First thing to check |
|---|---|
Trade rejected with -2015 |
API key permissions or IP whitelist — see Binance error codes. |
Trade rejected with -2019 |
Insufficient margin in the sub-account. |
| Webhook alert isn't placing trades | Strategy state is paused / learning / configuring. Check the strategy detail page. |
pair_lock_mismatch |
Strategy is locked to a different symbol than the alert sent. |
symbol_already_active |
Another of your strategies has an open trade on the same symbol. |
| Dashboard shows "disconnected" | Live update reconnect — usually transient. See Dashboard disconnects. |
| Trades visible on Binance but not in HookTrader | Positions opened outside HookTrader are never tracked. Use a dedicated sub-account. |
| Trail level reset after restart | HookTrader lost the in-memory trail state. See Open-trade state loss. |
Where to find logs#
- Notifications — user-visible errors and warnings.
- Strategy detail → Webhook log — every payload received, with translation result and outcome.
- Trade detail → Events — every state transition for that trade.
If none of that explains the issue, file a bug via the icon next to the ? in the dashboard header. The form attaches diagnostic information automatically.