Hi, Today there was an error - "trigger price should be 1.9% for CRUDEOILM17AUGFUT". Haven't seen this before... Has the rules changed (from "trigger price can be <=1.5% of order price")?
Hi @ramatius, Trigger price for a cover order must always be less than or equal to 1.9% of LTP. You can use this API to get trigger range. Trigger range for MCX has always been 1.9%, it has not changed.
Hi @sujith , There was no error when the CO was placed. The order got executed also. The SL-M order was pending (since the price hasn't reached). Then the cancelOrder was called on the SL-M order (so that it gets converted to market order). At that time this error popped up and the SL-M trigger continued to exist.
Is this the defined behavior? I expected that the initial CO would've got rejected with an out-of-range trigger price...
@ramatius, It is very unlikely that you will get this error for canceling order because while canceling the cover order, the backend will just modify that order to market. In short, it is very unlikely that this error occurred while placing the market order.
I am guessing, you might have tried to modify that order and error status message was updated for that order. Since API returns order_id in the above use case your algorithm must have considered that modify request was successful.
Trigger price for a cover order must always be less than or equal to 1.9% of LTP.
You can use this API to get trigger range.
Trigger range for MCX has always been 1.9%, it has not changed.
There was no error when the CO was placed. The order got executed also. The SL-M order was pending (since the price hasn't reached). Then the cancelOrder was called on the SL-M order (so that it gets converted to market order). At that time this error popped up and the SL-M trigger continued to exist.
Is this the defined behavior? I expected that the initial CO would've got rejected with an out-of-range trigger price...
It is very unlikely that you will get this error for canceling order because while canceling the cover order, the backend will just modify that order to market.
In short, it is very unlikely that this error occurred while placing the market order.
I am guessing, you might have tried to modify that order and error status message was updated for that order. Since API returns order_id in the above use case your algorithm must have considered that modify request was successful.