@Tushar11 Thanks for highlighting, I think we missed this. We will bring Auto-slicing with Iceberg+ to DOM soon - hope that there are no restrictions via the library.
Hello @Castelinojason ,
It would be helpful if you could share your registered account details with us via DM, so we can check this further and assist you accordingly. CC : @t7support
@Madiya_Khatri This is a generic issue which seems to have popped up after recent changes probably for iceberg +. I don’t recall the exact strike or timing of the error. But this what happened roughly with me.
I placed a 21 lot Banknifty option order as hedge leg first from the option chain for my option selling strategy. This went as an iceberg order as Banknifty freeze quantity is 20. Then I tried to sell another strike again quantity was 21. But this time the error like in the screenshot appeared. I then went to orders page to check whether order went through. Seeing that the order was successful I went again back to the option chain to fire the order which was then successful. This happened as I recall on 2 days. But while trading when an order fails the primary instinct is to get the order to the exchange and not record or log the failure unless I do the order firing with that intent. Hence I cannot really help with the exact strike and time now. But I will be watchful in the future. The screenshot I posted was from @Castelinojason who faced issue yesterday.
I was firing orders from my android mobile app and @Castelinojason was firing from his iphone app. There were no multiple clicking of the buy or sell button as explained to @Naman over phone yesterday.
1 Like