What type of algo notifications, alerts or updates would you like to receive via Telegram?
Anonymous Poll
41%
Only important notifications or alerts (eg. like order rejection, system failure etc)
68%
All possible notifications or alerts (eg. order entries, order exits etc)
The idea behind receiving only important notifications or updates is that, when a user gets all types of notifications and updates more frequently, he may tend to overlook or miss the more important and critical ones. So ideally, it may be better to get only the important notifications, alerts and updates.
What updates and alerts are the most important?
Anonymous Poll
39%
Successful entries
39%
Successful exits
51%
Order rejections
42%
Stoploss hit
24%
Target hit
42%
System health monitor alerts - Order API and Live Feed statuses
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