Modifying Sl Limit order in api is not working and getting responce successfull

[santhosh_kumar]

Hi i have trail sl using sl limit order it used to work fine but for me today one trade its not getting modifyed even its tried 2 or 3 times its not changed and not refelection on mobile as well but in the responce am getting successfull for that proper order id (250219010235713) on the same day its worked on other trades

[Ketan]

Hi @santhosh_kumar, you might be passing an invalid price or invalid trigger price in modify order payload.

For more reference you can refer to this thread →

Getting error response for Modify SL order request

Hi @AE9225 We reviewed the logs and found that for a stop-loss limit (SL) buy order, you are passing a trigger price that is greater than the limit price. This is incorrect for SL buy orders. If you intend to use a trigger price higher than the limit price, you should place a Limit order instead of an SL order. Please refer to the following article for detailed explanations of different order types: What are the different stock market order types on Upstox? You can verify the same through the…

If you are still facing an issue please feel free to comment in this thread.
Thanks!

[santhosh_kumar]

Hi @Ketan
ya i passed values properly can you give logs from yousr side so that we can confirm and if pass wrong value you should have check and give fail responce not my self

[Ketan]

@santhosh_kumar
This validation is performed at the exchange level, not on our end. When the exchange rejects order modification request, we provide a response through the order update WebSocket: Portfolio Stream Feed. Alternatively, you can check the order history using the given order ID: Order History.

@santhosh_kumar

getting successfull for that proper order id (250219010235713)

This means your modification order was placed successfully, but it does not guarantee that it will always be accepted. There are additional checks performed at a lower level beyond our control. That’s why we provide order updates via the WebSocket and the Order History API.

I hope this helps.

Thanks!

[santhosh_kumar]

@Ketan in this case why you are giving me responce before exchange giving you responce and above you mentiond one similar problem in that you mentioned you getting payload with “The limit price is worse than the trigger price” message why you are not giving this responce to user

if its a problem from exchange and lot of peoples affected from that did you rised any ticked to exchange ?

please dont simply tell you can check the aip failiour in websocket what is the time complexity for api and websocked feed responce so after making api request it wont change the status in websocket only in message its updating so how i can understand the oreder is failed with that payload

where did you guys studied engineering send aip req and get res from websocket if you are from big collage that does not mean whatever you are telling is correct and you are perfect

so at the end its not from your side so its not your problem GooD !
sorry its my mistake i should be more carefull when am chosing the api library

Thanks !

[Ketan]

@santhosh_kumar

why you are giving me responce before exchange giving you responce

Suppose you placed an AMO order on Saturday, and the order would be placed on the exchange on Monday In these cases, it’s not possible for the API call to wait for two days and provide a response from the exchange. This is why we suggest that users connect to a websocket and listen for updates. If the order fails after 2–3 days, or in the case of a GTT order, if it fails after four months, you can receive an update in websocket.

Thanks!