AlgoVesta › Glossary › Order rejection

Order Execution

Order rejection

An order rejection is the exchange or broker refusing to accept an order, returning an error instead of an order identifier; typical reasons are insufficient margin, a size below the minimum or not a multiple of the lot step, a price outside allowed limits, a symbol that is not tradable on that account, or an API key without trading permission.

Why it matters

A rejected order is not a partial success: nothing was placed, and if the platform does not surface the rejection the signal simply disappears while the bot looks healthy. In practice most "my bot is not trading" reports are chains of silent rejections: an account that ran out of free margin, a key created without futures permission, a forex symbol with a broker suffix, or a lot size the broker does not accept. The rejection message is the diagnosis, and it has to reach the person who can act on it.

How AlgoVesta handles it

AlgoVesta checks what it can before sending: the symbol's lot step and minimum notional, the size tolerance, the account's leverage cap and the bot's own risk rules. Anything the venue still rejects is recorded on the bot card and in the dashboard with the exchange's own message, translated into a plain explanation where the code is known (for example when the requested amount is below the minimum, the nearest valid amounts are shown). Blocked and rejected signals are counted, and a bot that blocks several signals without executing any within a day triggers a summary email. Rejections caused by your settings are separated from platform-side errors so you are not told to fix something that is not yours. Every rejection is kept with the signal it belonged to, so the history explains why a trade did not happen. See the crypto automation page and the help center.

Example

A trader sets $8 margin per signal at 1x on a Binance futures bot. The first signal for BTCUSDT is rejected before it is sent: the notional is below the exchange minimum. The bot card shows the reason with the minimum amount, the dashboard lists the signal as blocked, and no order reaches the exchange. After the margin is raised to $12 the next signal executes normally.

Common mistakes

In practice

See how AlgoVesta automates this