Double Quantity Purchased Issue (API: Exit position by tag)

Hi Team,
Today at 1 PM, I entered an Nifty short straddle at ATM (24500):
24500 CE: 361.30, SL: 390, Quantity: 25, Tag: NIFTY_STRADDLE_CE
24500 PE: 304.25, SL: 324, Quantity: 25 Tag: NIFTY_STRADDLE_PE

When stop loss hit for both positions, instead of 25, 50 quantity got purchased

Upon further investigating I found out that I had similar straddle at morning with same tags which were closed at 11 AM.

I used the the API, exit all position by tag:

The morning positions were closed at 11:00 AM, so I believe they should not have any impact on 01 PM positions.

I believe this is a bug in system, please get it checked.

Hi @Ranu_Pal, Could you please share your 6 digit user id for further investigation?

I think thats bit sensitive information to share in public.
Please share your email, will share over email.

@Ranu_Pal Feel free to send me a direct message

Explored the community portal, cant find any way to send a direct message to youā€¦ If you can, please send a direct message to me.

Shared in direct message.

Hello @Ranu_Pal,

We have reviewed the logs for the user ID you provided. The net buy quantity matches the net sell quantity for each instrument traded on December 4th.

It appears that you have short-sold 50 quantities earlier, which would explain why 50 quantities were purchased. We have recorded the same in our application log

Could you kindly verify all the trades executed on your end for December 4th? Additionally, if possible, please share the trade details via direct message so we can investigate further.

Thank you.

The quantity will certainly match as these trades were Intraday.

I have not sold 50 quantity.

I have sold 25 quantity at 11 AM , the position was closed due to stoploss (tag: STRADLE_ONE_PM_Nifty 50CE)

Sold again one lot (24500 CE) at 01 PM (tag: STRADLE_ONE_PM_Nifty 50CE)

This time when stop stoploss hits, 50 quantity got purchased.
The tag were same in both morning and afternoon trades.

Hi Team,
I am still looking for some update here.

@Ranu_Pal We have investigated the issue, and our team is actively working on a resolution. We will provide an update in this thread as soon as we have more information. Thank you for your patience.

1 Like