Redundant postback (repost)

@sujith thanks for the clarification.

The order of postbacks is first you will receive postback with UPDATE status and then OPEN after modification is successful.

We are receiving the OPEN postback first and then the UPDATE. this conflicting race condition is an issue.

Cant ignore the UPDATE postbacks as it will blind us in case of partial fills etc. Things gets even murkier in case we modify a partially filled order. Let me exemplify.

Modified a partial filled order to 259.65

03Jul18 10:30:37, PUT|apiKey=apKey, accessToken= accessToken, Url=https://api.kite.trade/orders/regular/180703000617209, Payload= exchange=NSE&tradingsymbol=HINDPETRO&transaction_type=SELL&order_type=LIMIT&product=CNC&quantity=100&price=259.65&validity=DAY

Post back received for the same. Here the status is UPDATE not OPEN

03Jul18 10:30:37, WebSocket_MessageReceived : {"type":"order","data":{"placed_by":"clientId","order_id":"180703000617209","exchange_order_id":"1100000001801439","parent_order_id":null,"status":"UPDATE","status_message":null,"order_timestamp":"2018-07-03 10:30:40","exchange_update_timestamp":null,"exchange_timestamp":"2018-07-03 10:30:40","variety":"regular","exchange":"NSE","tradingsymbol":"HINDPETRO","instrument_token":359937,"order_type":"LIMIT","transaction_type":"SELL","validity":"DAY","product":"CNC","quantity":100,"disclosed_quantity":0,"price":259.65,"trigger_price":0,"average_price":259.4,"filled_quantity":37,"pending_quantity":63,"cancelled_quantity":0,"market_protection":0,"meta":null,"tag":"f3f2b13d","guid":"qvYFlXD1peviuRW1","account_id":"clientId","unfilled_quantity":0,"app_id":106,"checksum":""}}

Received the stale postback with the status as UPDATE and the pre-modified price. This should have come first. Please check this at your end.

03Jul18 10:30:37, WebSocket_MessageReceived : {"type":"order","data":{"placed_by":"clientId","order_id":"180703000617209","exchange_order_id":"1100000001801439","parent_order_id":null,"status":"UPDATE","status_message":null,"order_timestamp":"2018-07-03 10:30:40","exchange_update_timestamp":null,"exchange_timestamp":"2018-07-03 10:30:40","variety":"regular","exchange":"NSE","tradingsymbol":"HINDPETRO","instrument_token":359937,"order_type":"LIMIT","transaction_type":"SELL","validity":"DAY","product":"CNC","quantity":100,"disclosed_quantity":0,"price":259.4,"trigger_price":0,"average_price":259.4,"filled_quantity":37,"pending_quantity":63,"cancelled_quantity":0,"market_protection":0,"meta":null,"tag":"f3f2b13d","guid":"qvYFlXD1peviuRW1","account_id":"clientId","unfilled_quantity":0,"app_id":106,"checksum":""}}

Received the response - this is fine

03Jul18 10:30:37, OrderId : {"status":"success","data":{"order_id":"180703000617209"}}

Given the OMS is designed as such dont think TR/Omnesys is going to change it. Potential workarounds:

• Give the actual postback status instead of UPDATE
  
• Maintain the chronology and send the messages as they come. (even then can we rule out a race condition?)
  
• A TAG property while modifying/cancelling order.
  

This is exactly why we can't stop sending UPDATE status postbacks.

Just send it once (when the order state is open) or keep the chronology correct, if possible.

The issue wherein order of postbacks is wrong is something happening because of OMS. We just relay postbacks as and when we receive the signal from OMS.

ya, tell them to fix it.

There are many intermediate statuses, sending the exact status may panic some other user's system as some people work on a specified set of statuses.

ok, I read it as a limitation at your end

Order tags already exist, a user can tag an order while placing it.

thats for entry orders only. I am requesting the same for order modification/cancellation too.


Overall the postback notification implementation is pretty impressive given it works across multiple platforms seamlessly and kudos to you for that. However much of the shine is lost due to the fact you have made the "state" exotic, redundant postbacks and random chronology.

Hey guys,

I was trying to work on the postback messages using the webhook method before I landed on this page..

Are you guys saying I can get messages for my order status using websocket? If so, where can I find more information on this. I have been searching for this in the Kite Documentations.

Thanks

@jjiteshh,
You can find the documentation about it here.

Okay the callback worked as expected...

Thanks