Why an alert did not trade

A rejection never changes an open trade's stop or targets.

Common reasons#

• Alert too old (stale): if alerts are routinely late, raise Ignore alerts older than.
• Trade already active: the strategy runs one trade at a time.
• Symbol already trading: another strategy holds it on the same account.
• Symbol doesn't match: the strategy is locked to another market. See Size and market.
• No stop-loss provided or Risk-% sizing needs a stop-loss: send a stop, or let HookTrader work one out.
• Stop-loss too wide: the stop exceeds the strategy's maximum distance.
• Price already beyond the stop-loss: price passed the stop first.
• Slippage too high or Fill beyond the stop-loss: the fill passed Skip the trade past or the stop. HookTrader closed it at once.
• Trailing stop would move the wrong way: the stop stayed put.
• Payload failed validation, Missing required fields or No mapping rule matched: the alert is unreadable. See How alerts are read and the Reference.
• Terms of service not accepted: accept them in Settings.

At your plan's open-positions limit, new entries are rejected. Exits and stop moves always go through. See Plans.

Binance errors#

Binance's refusals appear in Notifications. Paper accounts use the exchange's codes, such as Bybit's 110007 (not enough balance) and 110094 (under the minimum).

• API key rejected: the key must exist, have Enable Futures on and allow HookTrader's IP. Then click Verify permissions.
• API key format invalid or secret incorrect: reconnect, pasting the key and secret whole.
• Insufficient margin: add funds or trade smaller.
• Below the minimum order value or quantity: raise the risk, or pick a symbol with a smaller minimum.
• Above the maximum quantity or position: trade smaller or lower the leverage.
• Leverage not valid for this symbol: lower the leverage.
• Can't change margin mode: close the symbol's open position or order first.
• Rate limit: HookTrader resumes on its own.

We are alerted to errors on our side automatically.