SmartAPI REST
Segment: NFO
Product: NRML (CARRYFORWARD)
Variety: NORMAL
Order type: LIMIT

On 11-Sep-2026 at 09:20:09, the following order was rejected:
RMS:Rule: Position limit including CNC exceeds, Current:60, limit set:1

Rejected order:
SELL BANKNIFTY29SEP2654700CE
Quantity: 60
Product: NRML

However, three other position-opening orders for the same client code were completed within the same second:

Time Order Qty Status
09:20:08.583 BUY BANKNIFTY29SEP2656800CE 90 Complete
09:20:08.651 BUY BANKNIFTY29SEP2654600PE 90 Complete
09:20:08.924 SELL BANKNIFTY29SEP2656700PE 60 Complete
09:20:09.044 SELL BANKNIFTY29SEP2654700CE 60 Rejected

If the position limit on this account were genuinely 1, all four orders should have been rejected, not just the fourth order.

Also, at around 11:19 on the same day, the following order was accepted normally:

SELL BANKNIFTY29SEP2655200CE – Quantity 60 – NRML

This account regularly trades quantities of 60 and 90 every trading day.

Questions
Is a client-level position limit configured on this account? If yes, what is its value?
If the limit is 1, why did the three previous orders with quantities 90, 90, and 60 complete successfully within the same second?
Can rapid API activity on the same client code cause RMS to evaluate a new order against an incomplete or delayed position snapshot?

Please clarify what exactly Current:60, limit set:1 represents in this RMS rejection message.