Stop Orders on Binance Futures Are Fixed
If your stop loss, take profit, or trailing stop orders on Binance Futures started failing late last year while plain entries kept working, it was not your alert syntax. Binance changed how stop orders are placed. Autoview now speaks the new protocol, and your existing commands work again without a single edit.
What Binance changed
On December 9, 2025, Binance retired stop-type orders on its classic futures order endpoint. A STOP, STOP_MARKET, TAKE_PROFIT, or TRAILING_STOP_MARKET order sent the old way now comes back with error -4120 and a message telling you to use the Algo service. Market and limit entries were untouched. That split made the breakage genuinely confusing: the same alert that opened your position fine would fail the moment it tried to place the protective stop.
What we did
Autoview now routes every stop-type order on Binance Futures through Binance's Algo Order service. This covers both USDT-margined and COIN-margined contracts. Cancelling and listing carried over too, so a cancel command finds and clears an algo stop the same way it always handled the classic kind.
Nothing changes on your side. Stop loss, take profit, trailing stop, and conditional entry commands read exactly as they did before. The routing happens inside the integration, where it belongs.
Other fixes shipping with it
The same release repairs a cluster of order-handling problems we found while verifying exchange behavior command by command.
- Bybit spot: a stop or conditional order used to be accepted by the exchange and quietly stored with no trigger armed. It looked placed. It never fired. Autoview now sends the order filter Bybit requires, so a spot stop rests on the exchange as a real trigger order you can see.
- OANDA: fill-or-kill (
t=fok) and immediate-or-cancel (t=ioc) orders now work. And an order OANDA creates then immediately cancels, like a guaranteed stop priced too tight, now reports the cancellation reason instead of reading as a success. - Crypto.com: OCO orders place both legs correctly.
- Time in force: a new
tif=parameter sets time in force explicitly on exchanges that support it, and the Syntax Builder has a matching field. An unsupported value throws a clear error rather than guessing.
The Bybit one was the worst of these. An error you can read beats an order that pretends to exist.
What you need to do
Update the Autoview extension from the Chrome Web Store. Chrome usually updates extensions on its own within a few days, so you may already have it. Autoview's server-side webhook execution carries the same fixes.
Then test your stops. Fire an alert at a demo or testnet connection and watch the stop order land on the exchange. Several demo connections are free, so the test costs nothing.
Found something still misbehaving?
Tell us. We rebuilt our exchange verification this year around placing real orders and reading them back, and reports from live traders are how the remaining gaps get found. Write to support@autoview.com with the exchange, the command, and what you expected.