ANNOUNCEMENT:
Incase you have duplicate/same legs in the same algo, your algo will not work. We have made a change in the algos that will not allow the same legs to be configured in the algo. You can create a separate algo for the same legs
Incase you have duplicate/same legs in the same algo, your algo will not work. We have made a change in the algos that will not allow the same legs to be configured in the algo. You can create a separate algo for the same legs
Example:
You cannot add the same legs in the same algo.
For eg. ATM CE cannot be added twice in the case where stoplosses are different for each of the legs
You cannot add the same legs in the same algo.
For eg. ATM CE cannot be added twice in the case where stoplosses are different for each of the legs
On account of the heavy slippages that happened today in almost all accounts that took positions before 10:46 AM, especially in Zerodha accounts, we are planning to start testing SL-M orders for exits.
As SL-M orders are highly complex to manage in the case of Trailing SLs, combined premium exits and 'square off all' configurations, SL M order implementation may be a failure, and if successful, may be rolled out in a phased manner after extensive market testing
As SL-M orders are highly complex to manage in the case of Trailing SLs, combined premium exits and 'square off all' configurations, SL M order implementation may be a failure, and if successful, may be rolled out in a phased manner after extensive market testing
This media is not supported in your browser
VIEW IN TELEGRAM
FEATURE UPDATE:
Now you can specify Start time and End time down to seconds. (HH:MM:SS)
Now you can specify Start time and End time down to seconds. (HH:MM:SS)
This media is not supported in your browser
VIEW IN TELEGRAM
UI UPDATE:
You can change your strike price from the legs configuration table itself. No need to delete the leg and add a different one
You can change your strike price from the legs configuration table itself. No need to delete the leg and add a different one
WARNING
If the issue with Upstox continues, Upstox and Zerodha users of Quantiply, both will not be able to trade on Quantiply till the issue gets fixed from their side. This is due to interdependencies built into the system between the 2 brokers on our system
If the issue with Upstox continues, Upstox and Zerodha users of Quantiply, both will not be able to trade on Quantiply till the issue gets fixed from their side. This is due to interdependencies built into the system between the 2 brokers on our system
The Upstox team is fixing the issue. As soon as the issue is resolved, we will have the systems up and running
Systems back online for Upstox and Zerodha both. You can initiate trades now. If algo is disabled (mainly the case for Upstox users), you can enable them to take trades
Tutorial video on the Stoploss Trailing feature shared in the tweet. Do watch the video to understand the stoploss trailing feature fully
We have two good updates to share:
1. We have extended Quantiply’s introductory free plan by another month for all users. Quantiply will be free till 28th February 2021
2. The SL M order exits is successfully implemented for the platform and is ready to be deployed. We are publishing the feature on the platform today evening. It will be available for use tomorrow onwards
1. We have extended Quantiply’s introductory free plan by another month for all users. Quantiply will be free till 28th February 2021
2. The SL M order exits is successfully implemented for the platform and is ready to be deployed. We are publishing the feature on the platform today evening. It will be available for use tomorrow onwards
Avoid risks of larger slippages and broker outages with Stoploss Market orders.
Now available on Quantiply with stress free auto-modification of SL-M orders when used with the Trailing Stoploss feature
https://twitter.com/Quantiply_tech/status/1356968265969373185
Now available on Quantiply with stress free auto-modification of SL-M orders when used with the Trailing Stoploss feature
https://twitter.com/Quantiply_tech/status/1356968265969373185
This media is not supported in your browser
VIEW IN TELEGRAM
How to enable SL-M orders on Quantiply
POINTS TO NOTE [SL-M Orders]:
* SL-M order can be selected as an option from the Advanced Settings section at the bottom of the algo configuration page
* SL-M orders will be placed in the system as soon as the algo takes position
* Exit order type once selected cannot be modified while the trade is on. It can be modified only once the trade is closed and the algo is terminated
* Due to order modification and cancellation rate limits of the broker’s API, we have limited the Trailing Stoploss Frequency Interval to 15 seconds and onwards, and removed 1 second and 5 second intervals to any avoid failed modifications of SL-M orders
* The algo will modify the Stoploss Market orders in the system automatically when the stoplosses are trailed, in the case where Trailing Stoploss feature is enabled
* Do not cancel any trigger pending SL-M orders manually from the broker’s terminal. If cancelled manually, the algo will not be able to modify or re shoot Stoploss Market orders
* SL-M orders are only for stoploss exits and not for target exits. This feature should not be confused with Limit order types used for targets in general
* In the case of combined premium exits, all positions will be squared of with Market orders only and not SL-M orders
* In the case when SL M orders get cancelled in a ‘price out of execution range’ scenario, the algo will shoot market orders continuously till orders are executed. In such a case SL-M orders are not useful and will not be used
* SL-M order can be selected as an option from the Advanced Settings section at the bottom of the algo configuration page
* SL-M orders will be placed in the system as soon as the algo takes position
* Exit order type once selected cannot be modified while the trade is on. It can be modified only once the trade is closed and the algo is terminated
* Due to order modification and cancellation rate limits of the broker’s API, we have limited the Trailing Stoploss Frequency Interval to 15 seconds and onwards, and removed 1 second and 5 second intervals to any avoid failed modifications of SL-M orders
* The algo will modify the Stoploss Market orders in the system automatically when the stoplosses are trailed, in the case where Trailing Stoploss feature is enabled
* Do not cancel any trigger pending SL-M orders manually from the broker’s terminal. If cancelled manually, the algo will not be able to modify or re shoot Stoploss Market orders
* SL-M orders are only for stoploss exits and not for target exits. This feature should not be confused with Limit order types used for targets in general
* In the case of combined premium exits, all positions will be squared of with Market orders only and not SL-M orders
* In the case when SL M orders get cancelled in a ‘price out of execution range’ scenario, the algo will shoot market orders continuously till orders are executed. In such a case SL-M orders are not useful and will not be used
Quantiply.tech pinned «POINTS TO NOTE [SL-M Orders]: * SL-M order can be selected as an option from the Advanced Settings section at the bottom of the algo configuration page * SL-M orders will be placed in the system as soon as the algo takes position * Exit order type once…»