Here’s a poll on the SL TRAILING functionality. Do share your views.
(You can select multiple options)
(You can select multiple options)
What trailing frequency would you prefer?
Anonymous Poll
26%
Trail every second
34%
Trail every minute (backtestable on Stockmock)
22%
Every 10 second or in multiples of 10. Eg. option to select 10 secs, 20 secs, 30 secs etc
25%
Every 5 minutes or in multiples of 5. Eg. option to select 5 min, 10 min, 15 min etc
Side note:
Smaller the time frame, higher the chances of trailing SL getting hit
Higher the time frame, lower the chances of trailing SL getting hit
Smaller the time frame, higher the chances of trailing SL getting hit
Higher the time frame, lower the chances of trailing SL getting hit
Zerodha feed was down for 12 mins today, 12:13 PM onwards. Luckily for Quantiply's Zerodha users, the algos switched to the back up feed within 5 seconds
All feeds are down - brokers and backup feeds. There seems to be an issue with the feed coming from the exchange
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