Copy Trading v6.2.2

Release Date: August 23, 2026 Tags: ORDERS, TRADING, BUG-FIXES

Overview

Cancelling a copied order could report "Order not found" about an order that was open, funded and resting on the book. The search that looked for it read only the newest page of the account's order history — five thousand rows — and said nothing about the rest. Anything older than that page was simply not seen, and "I did not find it" was returned as though it meant "it is not there".

The follower's position stayed open and their funds stayed locked, and the only signal was a failure message that pointed at the wrong thing. On a busy account — a copier following an active provider crosses a page of history quickly — this was reachable within a day.

The cancel now walks every page, and where it does give up it says so instead of claiming the order does not exist. Requires Core v6.7.0.

Update Instructions

pnpm updator

Restart the backend afterwards. There is no database change and no migration.

Fixed

"Order not found" on an order that was open the whole time

The cancel path fetched the account's orders and looked for the one it had been asked to cancel. That fetch is a single query against the order store: the newest five thousand rows, with nothing said about whether there are more. An order older than that page could never be found, so the cancel returned failure while the order stayed OPEN, still resting in the book and still holding the follower's funds.

The two possible answers had been collapsed into one message. "It is not there" and "I stopped looking" are different facts, and only the first is something a customer can act on.

• Fixed the cancel searching one page of order history. It now walks pages until it finds the order or genuinely runs out of them.
• Changed the message for the case where the search is abandoned: it now says the account holds more open orders than one pass reads and points at the orders page, instead of reporting the order as missing.