`IB.client.getReqId()` returns already used ID

I am using IB.client.getReqId() to place my version of bracket orders and set parentId in target and stop loss orders.

But I have stumbled upon an error:

Traceback (most recent call last):
  (...)
  File "_", line 53, in bracket_order
    parent_trade: Trade = ib_client.placeOrder(contract, parent)
  File "/venv/lib/python3.6/site-packages/ib_insync/ib.py", line 528, in placeOrder
    assert trade.orderStatus.status not in OrderStatus.DoneStates
AssertionError

Which means that trade with such ID was found.

Parent order is created like that:

parent = MarketOrder(
    action, quantity,
    orderId=ib_client.client.getReqId(),
    transmit=False,
    conditionsIgnoreRth=False,
    outsideRth=False
)

Entire bracket_order function is copy of ib_insync.ib.IB.bracketOrder source with parent placed as MarketOrder instead of LimitOrder. So all but stopLoss are transmit=False. Orders are placed in order:

• parent,
• target,
• stop.

Is there a problem with IB that it start IB.client on wrong ID or does not update it properly?

[nemozny]

I can confirm the issue seems to be fixed with 0.9.66. I started tracking for orderId collisions, but since the update I haven’t seen any. In my previous comment I was NOT on 0.9.66.

[erdewit]

In the upcoming version of ib_insync the maximum orderId of open/completed orders is used to set the reqId sequence (see this code).

It seems the “nextValidId” from IB can’t be relied upon when TWS/gateway gets restarted.