Lot of accounts in Angel Broking getting the error "Exchange not enabled for this account" for API as well as manual orders. This issue has been escalated to Angel teams. We will update once we get a revert from them
This media is not supported in your browser
VIEW IN TELEGRAM
Stoploss Market (SL-M) orders
Scroll down to Advanced Settings, select the Exit order type as Stoploss Market (SL-M)
Scroll down to Advanced Settings, select the Exit order type as Stoploss Market (SL-M)
Angel Broking API seems to be down, we're checking the issue
Meanwhile keep an eye on your algos and manage manually if required. Existing SL M orders should not be a problem and would work as expected
All other brokers are running normally
Meanwhile keep an eye on your algos and manage manually if required. Existing SL M orders should not be a problem and would work as expected
All other brokers are running normally
Angel broking API is up now and running normally
IMPORTANT: ANGEL BROKING USERS
Please check your positions, there are a lot of errors coming from the API in a few accounts, manage, exit your positions manually if not executed
Please check your positions, there are a lot of errors coming from the API in a few accounts, manage, exit your positions manually if not executed
This media is not supported in your browser
VIEW IN TELEGRAM
*** FEATURE UPDATE ***
We have re-added 1 second trailing frequency interval for exit order type Market
This will help with faster, real-time trailing of stoplosses, but works only with Market order type and not SL-M
We have re-added 1 second trailing frequency interval for exit order type Market
This will help with faster, real-time trailing of stoplosses, but works only with Market order type and not SL-M
There seems to be a connectivity issue at our end, feed and algo not working. We're checking. Will update shortly
Issue is still being investigated, please monitor your trades and execute manually if required
My observations on what happened in Nifty 16450 CE yesterday
https://twitter.com/AbhiiShah/status/1428992051228512261
https://twitter.com/AbhiiShah/status/1428992051228512261
Twitter
Abhi Shah
What happened in 16450CE yesterday? My observations: Most SLM buy orders that triggered around 145 have been converted by the exchange from Market orders to Limit orders with a limit price of 0
SLimit order implementation
We are planning the SL implementation and will get started on the work today onwards.
It will be published to the platform once implemented properly and tested thoroughly. A timeline on which day it will be published will be difficult to guess as of today, but will share an update on it once we can
Temporary solutions to avoid ‘freak trades’, till S-Limit orders are implemented on Quantiply
1. Choose Exit order type SL-M. Once the algo has placed the SL-M orders. Modify them into S-Limit, with trigger price being the same and the limit price being 2-3% away from the trigger price
Here’s a quick explanation on how the SLimit order will work:
Say you’ve sold an option at 100, with SL Limit order with trigger price 120 and limit price 125. When the price reaches 120, your order will get executed at any price between 120 and 125.
What price you get depends on what next available best ask price your order gets matched above the trigger price. So, you may get a price of 123.05, or you may get a price of 125. If your order doesn’t get a fill at or below 125, your order will go into an Open status
If your order goes into Open status, you will need to manage manually, ie. modify the SLimit order into market order so your positions can square off
2. Choose exit order type Market. This is not the best solution, it wouldn’t guarantee safe exits. The assumption here would be that the spikes will not be captured in the price feed the algo receives. If the price spike is not seen in the data coming in the feed, the algo will not shoot a market order to square off positions
3. Choose liquid strikes. Though there is no functionality currently to choose +100 strikes only, for Nifty, trading in liquid strikes may pose a much lower risk
4. Reduce position size or pause trading till SLimit orders are implemented
What repercussions will modifying the order from SL M to S Limit have on the algo:
1. Only in the case where the order was modified (and not cancelled, and placed fresh SLimit order) the algo will show the average exit price on the Quantiply dashboard
2. Trailing features wont work as expected. If you modify SLM orders to SLimit while keeping trailing active on the algo the following will happen for specific brokers:
1. In Angel Broking and IIFL, the order will get modified with a trailed SL and become an SL-M order again
2. In Zerodha and Angel the trigger price will keep getting modified as it trails but the Limit price will have to be modified manually
We are planning the SL implementation and will get started on the work today onwards.
It will be published to the platform once implemented properly and tested thoroughly. A timeline on which day it will be published will be difficult to guess as of today, but will share an update on it once we can
Temporary solutions to avoid ‘freak trades’, till S-Limit orders are implemented on Quantiply
1. Choose Exit order type SL-M. Once the algo has placed the SL-M orders. Modify them into S-Limit, with trigger price being the same and the limit price being 2-3% away from the trigger price
Here’s a quick explanation on how the SLimit order will work:
Say you’ve sold an option at 100, with SL Limit order with trigger price 120 and limit price 125. When the price reaches 120, your order will get executed at any price between 120 and 125.
What price you get depends on what next available best ask price your order gets matched above the trigger price. So, you may get a price of 123.05, or you may get a price of 125. If your order doesn’t get a fill at or below 125, your order will go into an Open status
If your order goes into Open status, you will need to manage manually, ie. modify the SLimit order into market order so your positions can square off
2. Choose exit order type Market. This is not the best solution, it wouldn’t guarantee safe exits. The assumption here would be that the spikes will not be captured in the price feed the algo receives. If the price spike is not seen in the data coming in the feed, the algo will not shoot a market order to square off positions
3. Choose liquid strikes. Though there is no functionality currently to choose +100 strikes only, for Nifty, trading in liquid strikes may pose a much lower risk
4. Reduce position size or pause trading till SLimit orders are implemented
What repercussions will modifying the order from SL M to S Limit have on the algo:
1. Only in the case where the order was modified (and not cancelled, and placed fresh SLimit order) the algo will show the average exit price on the Quantiply dashboard
2. Trailing features wont work as expected. If you modify SLM orders to SLimit while keeping trailing active on the algo the following will happen for specific brokers:
1. In Angel Broking and IIFL, the order will get modified with a trailed SL and become an SL-M order again
2. In Zerodha and Angel the trigger price will keep getting modified as it trails but the Limit price will have to be modified manually
As we plan to implement, test & publish S-Limit orders this week as an urgently required feature, some other functionality that we planned to make available this week or test this week, will get pushed to next week
So the following activities gets pushed to next week:
1. Credits for Referral benefits (You will receive credits for the referred users by end of next week)
2. Wait & Trade testing
3. Testing of error messages on the dashboard
So the following activities gets pushed to next week:
1. Credits for Referral benefits (You will receive credits for the referred users by end of next week)
2. Wait & Trade testing
3. Testing of error messages on the dashboard
This media is not supported in your browser
VIEW IN TELEGRAM
*** FEATURE UPDATE ***
SL-LIMIT ORDER TYPE
You can configure SL-Limit order type for stoploss exit orders, under the Advanced Settings section, on the algo configuration page. Once selected, a user can define the buffer between trigger and limit price in points from the trigger price or percentage of the trigger price. Once points or percentage setting is selected, specify the value of the buffer.
A user can also specifiy after how many seconds of the SL-Limit order going into Open status should the algo fire a Market order to execute the trade. A trade goes into ‘Open’ status as soon as the trigger price is crossed
The Market order that may be fired after the specified number of seconds, will execute only the pending quantity that did not get filled by the Limit order.
Minimum value for the buffer value and Exit with Market order in (N) secs value is 0. There is no max value cap for both
SL-Limit settings can be configured for each algo individually, depending on the trader's requirement
SL-LIMIT ORDER TYPE
You can configure SL-Limit order type for stoploss exit orders, under the Advanced Settings section, on the algo configuration page. Once selected, a user can define the buffer between trigger and limit price in points from the trigger price or percentage of the trigger price. Once points or percentage setting is selected, specify the value of the buffer.
A user can also specifiy after how many seconds of the SL-Limit order going into Open status should the algo fire a Market order to execute the trade. A trade goes into ‘Open’ status as soon as the trigger price is crossed
The Market order that may be fired after the specified number of seconds, will execute only the pending quantity that did not get filled by the Limit order.
Minimum value for the buffer value and Exit with Market order in (N) secs value is 0. There is no max value cap for both
SL-Limit settings can be configured for each algo individually, depending on the trader's requirement
Some traders on Quantiply haven’t started using SL Limit orders for exits yet. We request everyone to use only SL Limit orders for individual leg exits on all algos, to considerably reduce the chances of getting hit by a ‘freak trade’
In terms of recommendations on what can be the buffer value between trigger price and limit price, and how many seconds timeout should be configured for Market orders, we don’t have any data to recommend ideal settings.
The buffer value can be higher on high premium and low liquidity days like Fridays. Buffer values can also be kept higher on Thursday’s as well, if you’re trading at the ATM
NOTE:
1. N seconds countdown starts as soon as the ‘Trigger Pending’ position goes into ‘Open’ status once it reaches the Trigger price
2. The Limit price is calculated from the Trigger price. Example (1): For sell positions, for settings where buffer is set in Points and buffer value is set to 10, and calculated SL ie. Trigger price is 100. The limit price in this case will be 110 (ie. 10 points from the trigger price). Example (2): For sell positions, for settings where buffer is set in Percentage and buffer value 5, and calculated SL ie. Trigger price is 100. The limit price in this case will be 105 (ie. 5% of the trigger price)
3. A simple explanation on how an SL Limit order works is shared here: How SL Limit works
You can find detailed explanations on support.zerodha.com
4. It is possible that only partial quantities get executed at the Limit price or between the Trigger and Limit price, the Market order shot out after (N) seconds will execute the pending quantity below, at, or above the limit price
5. To understand how to access and configure the SL Limit order type settings, check out the SL-LIMIT ORDER TYPE - Feature Update post on the Telegram channel
In terms of recommendations on what can be the buffer value between trigger price and limit price, and how many seconds timeout should be configured for Market orders, we don’t have any data to recommend ideal settings.
The buffer value can be higher on high premium and low liquidity days like Fridays. Buffer values can also be kept higher on Thursday’s as well, if you’re trading at the ATM
NOTE:
1. N seconds countdown starts as soon as the ‘Trigger Pending’ position goes into ‘Open’ status once it reaches the Trigger price
2. The Limit price is calculated from the Trigger price. Example (1): For sell positions, for settings where buffer is set in Points and buffer value is set to 10, and calculated SL ie. Trigger price is 100. The limit price in this case will be 110 (ie. 10 points from the trigger price). Example (2): For sell positions, for settings where buffer is set in Percentage and buffer value 5, and calculated SL ie. Trigger price is 100. The limit price in this case will be 105 (ie. 5% of the trigger price)
3. A simple explanation on how an SL Limit order works is shared here: How SL Limit works
You can find detailed explanations on support.zerodha.com
4. It is possible that only partial quantities get executed at the Limit price or between the Trigger and Limit price, the Market order shot out after (N) seconds will execute the pending quantity below, at, or above the limit price
5. To understand how to access and configure the SL Limit order type settings, check out the SL-LIMIT ORDER TYPE - Feature Update post on the Telegram channel
*** FEATURE UPDATE ***
WAIT & TRADE
What is the Wait & Trade feature?
To take entries, the algo will wait for the price to go up or down from the reference price, by a set percentage or points configured for the specific legs. The reference price is the price captured by the algo at the start time.
Important points related to Wait & Trade shared by mail and in the Telegram discussion group
WAIT & TRADE
What is the Wait & Trade feature?
To take entries, the algo will wait for the price to go up or down from the reference price, by a set percentage or points configured for the specific legs. The reference price is the price captured by the algo at the start time.
Important points related to Wait & Trade shared by mail and in the Telegram discussion group
*** FEATURE UPDATE ***
Error/rejection messages in the ‘Live’ data section
You can now view error or rejection messages in the ‘Live’ data section of your dashboard. Hover your mouse or tap on the warning icon to view the error or rejection message.
2 important scenarios related to this feature have been sent by mail and posted in the discussion group
Error/rejection messages in the ‘Live’ data section
You can now view error or rejection messages in the ‘Live’ data section of your dashboard. Hover your mouse or tap on the warning icon to view the error or rejection message.
2 important scenarios related to this feature have been sent by mail and posted in the discussion group
Go through this message before you trade on Monday!
Here’s an important point related to error messages and treatment of orders executed with errors and without errors.
There are 2 key differences in the system with the new updates.
Scenario 1: Wait & Trade is configured
In this scenario if there is an error or rejection in one of the legs, the other legs that may have been executed properly without errors, will have the stoplosses placed in the terminal or at Quantiply’s end, and will exit as per configured settings. Only the leg which failed to execute due to an error or rejection, can be manually entered from the terminal, and stoplosses can be placed manually. For all other correctly executed legs, the algo will functional normally as expected
Scenario 2: Wait & Trade is NOT configured
In this scenario if there is an error or rejection in one of the legs, the other legs that may have been executed properly without errors, will go into a ‘Waiting’state. In this case, the algo will not function as expected. You can manually manage positions from there on and terminate the algo. Or you can square off all positions manually from the terminal, and re-take the same positions in a new algo
In future updates, we will address Scenario 2 to allow the algo to manage positions with the algo itself, which may have been executed without errors or rejections
Here’s an important point related to error messages and treatment of orders executed with errors and without errors.
There are 2 key differences in the system with the new updates.
Scenario 1: Wait & Trade is configured
In this scenario if there is an error or rejection in one of the legs, the other legs that may have been executed properly without errors, will have the stoplosses placed in the terminal or at Quantiply’s end, and will exit as per configured settings. Only the leg which failed to execute due to an error or rejection, can be manually entered from the terminal, and stoplosses can be placed manually. For all other correctly executed legs, the algo will functional normally as expected
Scenario 2: Wait & Trade is NOT configured
In this scenario if there is an error or rejection in one of the legs, the other legs that may have been executed properly without errors, will go into a ‘Waiting’state. In this case, the algo will not function as expected. You can manually manage positions from there on and terminate the algo. Or you can square off all positions manually from the terminal, and re-take the same positions in a new algo
In future updates, we will address Scenario 2 to allow the algo to manage positions with the algo itself, which may have been executed without errors or rejections
This is a repeat announcement for users who still haven't switched to SL Limit orders.
Change your Exit order type from SL Market to SL Limit.
We're seeing some errors with Zerodha clients who are still using SL M orders. Zerodha is rejecting SL M orders. You are supposed to switch to SL Limit orders completely
Here is an old post instructing you to do the same: https://t.me/quantiply/178
Change your Exit order type from SL Market to SL Limit.
We're seeing some errors with Zerodha clients who are still using SL M orders. Zerodha is rejecting SL M orders. You are supposed to switch to SL Limit orders completely
Here is an old post instructing you to do the same: https://t.me/quantiply/178
⚠️ IMPORTANT ANNOUNCEMENT ⚠️
Removal of Stoploss Market (SL-M) order type
Based on the latest disclosure by NSE, SL-M order type will be discontinued for Options on Monday, 27th September 2021. On Quantiply, SL-M order type will also be discontinued effective after market, today.
Additionally, SL-M is being removed, as, Zerodha is already disallowing SL-M orders for Options, and other brokers may soon too. Removal of SL-M order type from Quantiply, will help avoid any rejections in order placement coming from Zerodha and other brokers.
All users are requested to re-configure your Exit order type setting to SL-Limit immediately after market today to avoid issues during live market hours going forward
All existing SL-M exit order type configurations will be changed to SL-Limit, exit order type, with default settings:
1. Buffer value in: Percentage
2. Buffer value: 5%,
3. ‘N’ seconds time out value: 15 seconds
Note: These settings will be applied only to algos where SL-M is configured as Exit order type. It will NOT affect any existing SL-Limit, exit order type settings.
You are requested to modify the Exit order type settings as per your preferences, after market hours today.
Removal of Stoploss Market (SL-M) order type
Based on the latest disclosure by NSE, SL-M order type will be discontinued for Options on Monday, 27th September 2021. On Quantiply, SL-M order type will also be discontinued effective after market, today.
Additionally, SL-M is being removed, as, Zerodha is already disallowing SL-M orders for Options, and other brokers may soon too. Removal of SL-M order type from Quantiply, will help avoid any rejections in order placement coming from Zerodha and other brokers.
All users are requested to re-configure your Exit order type setting to SL-Limit immediately after market today to avoid issues during live market hours going forward
All existing SL-M exit order type configurations will be changed to SL-Limit, exit order type, with default settings:
1. Buffer value in: Percentage
2. Buffer value: 5%,
3. ‘N’ seconds time out value: 15 seconds
Note: These settings will be applied only to algos where SL-M is configured as Exit order type. It will NOT affect any existing SL-Limit, exit order type settings.
You are requested to modify the Exit order type settings as per your preferences, after market hours today.