Duplicate ClientOrderId Error on Script Restart with Existing Position (Binance Testnet)

[daydayup789]

I'm conducting real-time trading tests using the Binance testnet (script: binance_futures_testnet_ema_cross.py).

When I have open positions, starting the trading script triggers the following error:

[ERROR] TESTER-001.ExecEngine: Duplicate ClientOrderId('O-20250714-074501-001-001-1') detected: OrderStatusReport(account_id=BINANCE-USDT_FUTURE-master, instrument_id=ETHUSDT-PERP.BINANCE, client_order_id=O-20250714-074501-001-001-1, order_list_id=None, venue_order_id=4843909235, venue_position_id=None, order_side=SELL, order_type=MARKET, contingency_type=NO_CONTINGENCY, time_in_force=GTC, expire_time=None, order_status=FILLED, price=0, trigger_price=0, trigger_type=LAST_PRICE, limit_offset=None, trailing_offset=None, trailing_offset_type=NO_TRAILING_OFFSET, quantity=0.010, filled_qty=0.010, leaves_qty=0.000, display_qty=None, avg_px=3046.60000, post_only=False, reduce_only=False, cancel_reason=None, report_id=3efd1411-6613-4597-a6d2-0b9e4727f73d, ts_accepted=1752479102094000128, ts_triggered=0, ts_last=1752479102094000128, ts_init=1752485076941484035)

Due to an 8-hour time zone difference, 074501 corresponds to my local time 154501, which matches the selected time record in the screenshot below:

Previously, I tested on Windows 10 (where CTRL+C could not gracefully shut down the script). Then I installed WSL2 and ran the test under Linux.
Since a position was created when I started the script on Windows 10, running the script in WSL2 does not produce an error and closes all positions properly on exit.

I also tested distributed trading (i.e., running the script simultaneously on Windows 10 and Linux). Since both tried to place orders on the same bar, errors occurred on both sides, but no detailed logs were preserved.

Later, once the account has an existing position, I can no longer start the script—the same error mentioned above occurs.
If I manually close all positions in the account, the script starts and ends normally (at this point, I had two strategies configured: Strategy A closes positions in on_stop, Strategy B does nothing in on_stop).
After stopping, there are remaining positions from Strategy B.

Trying to restart the script in this case also leads to the same error as before. All the errors point to the same ClientOrderId('O-20250714-074501-001-001-1').

[daydayup789]

in LiveExecEngineConfig, add filtered_client_order_ids=[ClientOrderId('O-20250714-074501-001-001-1')]