New feature: Client wise Stoploss & Target
RELEASE NOTES:
I. Settings:
Click on Clientwise P&L seen on the top of the main page to view P&L of all client IDs configured on your Quantiply account.
Click on the Settings button ‘⚙️ ‘ under the individual Client ID section. It will open a pop up where the Stoploss setting and the Target setting can be defined, for a particular Client ID.
II. How it indicates Client id wise SL or Target is hit:
Upon hitting the ClientIDwise Target, the individual client id card turns green, and, upon hitting ClientIDwise Stoploss, the individual client id card turns red, to indicate Target or Stoploss type of exit.
This functionality also helps view client id wise live Total MTM.
Upon click on the individual client id card, the algo table will filter out and show only those algos that are configured for the selected client id. So, click on any single client id or multiple client ids will act like a filter. The filter can be deactivated by deselecting the client id again, which will in turn show all the algos in the algos table.
III. Other important points:
1. Say you have a total of 5 algos enabled for a particular client id, 3 of them are currently active, and the other 2 a configured to run at a later time in the day. If, the clientID wise SL or target is hit while the 3 algos are running, the 3 algos will immediately exit, and the other 2 algos which were configured to run later in the day, will NOT fire ie. those other 2 algos will not run as client ID wise SL or Target is already hit.
2. In the above scenario, if you want the other 2 algos to run, then the client id wise Stoploss or Target setting can be modifed to a higher number. Once the SL or Target setting is increased, the client id wise SL and Target counters are reset and the positions in the other 2 algos will be taken.
3. ClientID wise Stoploss and Target can be modified while algos are active and trades are open.
4. This functionality considers all active algos running on a particular client id, in calculating the total current MTM, whether its a Positional algo running from previous days or current day Intraday algos. It will consider the MTM of all currently active individual algos. For example, if your client id wise Stoploss is set to Rs. -10,000, and you have 2 algos running - 1 positional algo from yesterday and 1 intraday algo which entered trades today. If the combined MTM of both these algos becomes Rs. -10,000, then both these algos will exit immediately.
5. Once all algos exit upon hitting the Target or Stoploss for the current day, the Client ID wise Target or Stoploss counter will get reset by midnight on the same day, and fresh PNL calculations will start the next day morning as per the Target or SL settings given by the user.
RELEASE NOTES:
I. Settings:
Click on Clientwise P&L seen on the top of the main page to view P&L of all client IDs configured on your Quantiply account.
Click on the Settings button ‘⚙️ ‘ under the individual Client ID section. It will open a pop up where the Stoploss setting and the Target setting can be defined, for a particular Client ID.
II. How it indicates Client id wise SL or Target is hit:
Upon hitting the ClientIDwise Target, the individual client id card turns green, and, upon hitting ClientIDwise Stoploss, the individual client id card turns red, to indicate Target or Stoploss type of exit.
This functionality also helps view client id wise live Total MTM.
Upon click on the individual client id card, the algo table will filter out and show only those algos that are configured for the selected client id. So, click on any single client id or multiple client ids will act like a filter. The filter can be deactivated by deselecting the client id again, which will in turn show all the algos in the algos table.
III. Other important points:
1. Say you have a total of 5 algos enabled for a particular client id, 3 of them are currently active, and the other 2 a configured to run at a later time in the day. If, the clientID wise SL or target is hit while the 3 algos are running, the 3 algos will immediately exit, and the other 2 algos which were configured to run later in the day, will NOT fire ie. those other 2 algos will not run as client ID wise SL or Target is already hit.
2. In the above scenario, if you want the other 2 algos to run, then the client id wise Stoploss or Target setting can be modifed to a higher number. Once the SL or Target setting is increased, the client id wise SL and Target counters are reset and the positions in the other 2 algos will be taken.
3. ClientID wise Stoploss and Target can be modified while algos are active and trades are open.
4. This functionality considers all active algos running on a particular client id, in calculating the total current MTM, whether its a Positional algo running from previous days or current day Intraday algos. It will consider the MTM of all currently active individual algos. For example, if your client id wise Stoploss is set to Rs. -10,000, and you have 2 algos running - 1 positional algo from yesterday and 1 intraday algo which entered trades today. If the combined MTM of both these algos becomes Rs. -10,000, then both these algos will exit immediately.
5. Once all algos exit upon hitting the Target or Stoploss for the current day, the Client ID wise Target or Stoploss counter will get reset by midnight on the same day, and fresh PNL calculations will start the next day morning as per the Target or SL settings given by the user.
New feature: Square off individual legs with multi-select option
This functionality enables you to exit (ie. Square off) selected legs while those Positions are open.
RELEASE NOTES:
I. How to use:
Select individual ‘Open’ legs or use the Select all option to select Open legs. Once the desired legs are selected, click on ‘Exit selected legs’ to immediately square off the selected Open legs.
Open legs mean positions that are currently open (ie. the trade is active for that leg)
II. Important points:
1. This option will only Square off Open legs and also cancel any open SL orders of the same legs.
2. This option does NOT Cancel or de-activate any Pending Wait & Trade or Re-entry orders. It only operates on Open positions
Use case:
1. This functionality can be helpful in squaring of buy hedges bought to avail margin benefits, once the consecutive sell legs have exited.
This functionality enables you to exit (ie. Square off) selected legs while those Positions are open.
RELEASE NOTES:
I. How to use:
Select individual ‘Open’ legs or use the Select all option to select Open legs. Once the desired legs are selected, click on ‘Exit selected legs’ to immediately square off the selected Open legs.
Open legs mean positions that are currently open (ie. the trade is active for that leg)
II. Important points:
1. This option will only Square off Open legs and also cancel any open SL orders of the same legs.
2. This option does NOT Cancel or de-activate any Pending Wait & Trade or Re-entry orders. It only operates on Open positions
Use case:
1. This functionality can be helpful in squaring of buy hedges bought to avail margin benefits, once the consecutive sell legs have exited.
⚠️ ERROR for ZERODHA Clients ⚠️
Lot of -:NetworkException:No response from server with error code: ECONNABORTED coming for most Zerodha users continuously. Zerodha has been notified, we are waiting for their response
Orders will not get placed because of this error in majority of the cases. Incase the order is executed and Zerodha has returned entry price, then the algo will work
Lot of -:NetworkException:No response from server with error code: ECONNABORTED coming for most Zerodha users continuously. Zerodha has been notified, we are waiting for their response
Orders will not get placed because of this error in majority of the cases. Incase the order is executed and Zerodha has returned entry price, then the algo will work
ZERODHA -:NetworkException:No response from server with error code: ECONNABORTED ERROR seems resolved, but no confirmation from their side
Share your algo page links if you want to get your Zerodha algos reset for re-use
Share your algo page links if you want to get your Zerodha algos reset for re-use
⚠️ There seems to be a delay in execution with FINVASIA. Broker has confirmed a backend issue. Once resolved, we will announce. This issue is only with FINVASIA, all other brokers working fine ⚠️
⚠️FINVASIA issue resolved according to Finvasia. New orders are getting placed. Pending orders are still showing pending and might get timed out automatically.
Finvasia users can send the algo page links to get their algos reset so it can be re-used. DM algo page links to Abhi⚠️
Finvasia users can send the algo page links to get their algos reset so it can be re-used. DM algo page links to Abhi⚠️
⚠️FINVASIA seeing errors again, please monitor your trades⚠️
This media is not supported in your browser
VIEW IN TELEGRAM
📣 Updated WAIT & TRADE + RE-ENTRY/RE-EXECUTE functionality 📣
1. TERMINOLOGY CHANGE:
The term RE-ASAP has been changed to RE-EXECUTE. The functionality remains the same, only the terminology has changed.
2. LOGIC CHANGE:
RE-COST type re-entry logic change.
2.1 Old logic:
For multiple re-entries, the re-entry price considered by the algo was the original entry price of the first trade
2.2. New logic:
For multiple re-entires, the re-entry price considered by the algo for the upcoming re-entry would be the average entry price of the previous trade/re-entry, and NOT the average entry price of the very first entry (original entry).
This logic has been updated as per the current logic on Stockmock
3. Updated Wait & Trade with Re-entry/Re-Execute features (as per Stockmock’s current functionality):
3.1. The following RE-Entry types can be enabled without Wait & Trade enabled for individual leg Square off:
1. RE COST
2. RE EXECUTE
3. RE COST REVERSE
4. RE EXECUTE REVERSE
3.2. The following RE-Entry types can be enabled with Wait & Trade enabled for individual leg Square off:
1. RE COST
2. W&T RE COST
3. RE EXECUTE
4. W&T RE EXECUTE
5. RE COST REVERSE
6. W&T RE COST REVERSE
7. RE EXECUTE REVERSE
8. W&T RE EXECUTE REVERSE
3.3. The following Re-entry types can be enabled with or without Wait & Trade enabled for the option Square off all legs:
1. RE EXECUTE
2. RE EXECUTE REVERSE
⚠️❗️ Please note, currently for the Square off all legs & RE EXECUTE option, even if Wait & Trade is being used, Wait & Trade condition is only applied for the first original entry, once the SL of any one of the legs hits, all open legs will get squared off and all legs will get re-executed without wait & trade again. This functionality is being modified to work with W&T condition for all re-entries also. It will be tested and launched in 2 days time ❗️⚠️
1. TERMINOLOGY CHANGE:
The term RE-ASAP has been changed to RE-EXECUTE. The functionality remains the same, only the terminology has changed.
2. LOGIC CHANGE:
RE-COST type re-entry logic change.
2.1 Old logic:
For multiple re-entries, the re-entry price considered by the algo was the original entry price of the first trade
2.2. New logic:
For multiple re-entires, the re-entry price considered by the algo for the upcoming re-entry would be the average entry price of the previous trade/re-entry, and NOT the average entry price of the very first entry (original entry).
This logic has been updated as per the current logic on Stockmock
3. Updated Wait & Trade with Re-entry/Re-Execute features (as per Stockmock’s current functionality):
3.1. The following RE-Entry types can be enabled without Wait & Trade enabled for individual leg Square off:
1. RE COST
2. RE EXECUTE
3. RE COST REVERSE
4. RE EXECUTE REVERSE
3.2. The following RE-Entry types can be enabled with Wait & Trade enabled for individual leg Square off:
1. RE COST
2. W&T RE COST
3. RE EXECUTE
4. W&T RE EXECUTE
5. RE COST REVERSE
6. W&T RE COST REVERSE
7. RE EXECUTE REVERSE
8. W&T RE EXECUTE REVERSE
3.3. The following Re-entry types can be enabled with or without Wait & Trade enabled for the option Square off all legs:
1. RE EXECUTE
2. RE EXECUTE REVERSE
⚠️❗️ Please note, currently for the Square off all legs & RE EXECUTE option, even if Wait & Trade is being used, Wait & Trade condition is only applied for the first original entry, once the SL of any one of the legs hits, all open legs will get squared off and all legs will get re-executed without wait & trade again. This functionality is being modified to work with W&T condition for all re-entries also. It will be tested and launched in 2 days time ❗️⚠️
⚠️ Wait & Trade data not displaying in the Wait & Trade data column. There is no issue with the functionality, this is just a UI issue with displaying the data. It's being fixed asap ⚠️
⚠️ Wait & Trade data is now being displayed properly on the UI. Refresh the page to see the data ⚠️
⚠️ Update: Wait & Trade + RE EXECUTE + Square off all legs ⚠️
When Wait & Trade + RE EXECUTE + Square off all legs is configured together, note that the Wait & Trade condition will get applied to the re-entry orders as well. Which means, that after the SL is hit, the whole entry logic is re-executed. Which is - strike selection, calculating entry price after applying wait & trade condition to the reference price.
When Wait & Trade + RE EXECUTE + Square off all legs is configured together, note that the Wait & Trade condition will get applied to the re-entry orders as well. Which means, that after the SL is hit, the whole entry logic is re-executed. Which is - strike selection, calculating entry price after applying wait & trade condition to the reference price.
⚠️ For IIFL users: Some open positions have been closed by IIFL, with error message: "16795 : Order cancelled due to voluntary close out.". We're checking with IIFL what this means. Meanwhile if there are any naked open positions, please square them off manually⚠️
⚠️ For IIFL users: As per IIFL, only pending Limit/SL Limit orders are cancelled. Open positions are still open and will stay open.
Option 1: You can manually place the SL orders that got cancelled directly from the XTS terminal, and let the algo run as it is
Option 2: If trailing and combined premium exits are involved then you can Square off all positions and terminate the algo⚠️
SAFEST OPTION: Option 2
Option 2 will help avoid any kind of double orders to get triggered, 1 that is manual and 1 that is triggered by the algo. This is specific to certain scenarios and not all
Option 1: You can manually place the SL orders that got cancelled directly from the XTS terminal, and let the algo run as it is
Option 2: If trailing and combined premium exits are involved then you can Square off all positions and terminate the algo⚠️
SAFEST OPTION: Option 2
Option 2 will help avoid any kind of double orders to get triggered, 1 that is manual and 1 that is triggered by the algo. This is specific to certain scenarios and not all
⚠️ For IIFL users: For algos where Entry order type and Exit order type is MARKET, will not be affected and those algos dont need to be square off and terminated ⚠️
⚠️ As one would notice, for BANKNIFTY strikes above 40000 and below 30900 occur in multiples of 500, instead of 100, for most weekly expiry contracts for this month and the upcoming month.
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens as the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
SOLUTION:
By Wednesday evening, we will be giving an option to enter 500 multiple strikes only, in BANKNIFTY while configuring the leg-wise strike selection. This will enable positions to be taken in strikes that occur in multiples of 500 while being closest to the configured strike level like OTM20 or OTM21 and so on. A detailed explnation of this will be shared on Wednesday when this functionality is published. ⚠️
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens as the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
SOLUTION:
By Wednesday evening, we will be giving an option to enter 500 multiple strikes only, in BANKNIFTY while configuring the leg-wise strike selection. This will enable positions to be taken in strikes that occur in multiples of 500 while being closest to the configured strike level like OTM20 or OTM21 and so on. A detailed explnation of this will be shared on Wednesday when this functionality is published. ⚠️
This media is not supported in your browser
VIEW IN TELEGRAM
📣 New Functionality: Select 500 / 100 multiple strikes in Banknifty & Nifty respectively while configuring LEGS.📣
While configuring the Legs in the algo, one can choose the option to select and take positions only in strikes that occur in the 500/100 multiples
[continued...]
While configuring the Legs in the algo, one can choose the option to select and take positions only in strikes that occur in the 500/100 multiples
[continued...]
📣 New Functionality: Select 500 / 100 multiple strikes in Banknifty & Nifty respectively while configuring LEGS. 📣
THE ISSUE:
As one would notice, for BANKNIFTY strikes above 40000 and below 30900 occur in multiples of 500, instead of 100, for most weekly expiry contracts for this month and the upcoming month.
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens because the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
THE SOLUTION:
The solution to this issue would be to try and select only those active strikes which occur only in the multiples of 500. And for the algo to do that, we have added an optional functionality to select only 500 or 100 multiple strikes for Banknifty and Nifty respectively.
So, while configuring the Legs in the algo, one can choose the option to select only 500/100 multiple strikes.
Example:
Say the Banknifty spot is currently at 38319, and one of the legs configured in the algo is OTM 20. This means that the ATM is 38300 and the OTM 20 is 40300.
Since beyond the 40000 strike, only strikes that are active occur in the multiple of 500, hence the next active strike after 40000 is 40500. But the algo will not take entries, as, based on the Leg configured, the strike selected is 40300, which is inactive.
In this case, if the option to select 500/100 multiple strikes is selected while configuring the leg, the algo will automatically take positions in the strike which is closest to 40300 but at the same time in the direction which is closer to the ATM.
Hence the algo, will take the entry in 40000 instead of shooting an order for 40300, as 40000 is the closest strike to 40300 and is also closer to the ATM than 40300 or even 40500.
HOW TO CONFIGURE THIS SETTING?
Click on the symbol selection dropdown menu > click on Legs > select the strike & select the option 500/100 multiple under Specific strike selection option. Once selected, click Done, and click Save to save the algo settings.
THE ISSUE:
As one would notice, for BANKNIFTY strikes above 40000 and below 30900 occur in multiples of 500, instead of 100, for most weekly expiry contracts for this month and the upcoming month.
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens because the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
THE SOLUTION:
The solution to this issue would be to try and select only those active strikes which occur only in the multiples of 500. And for the algo to do that, we have added an optional functionality to select only 500 or 100 multiple strikes for Banknifty and Nifty respectively.
So, while configuring the Legs in the algo, one can choose the option to select only 500/100 multiple strikes.
Example:
Say the Banknifty spot is currently at 38319, and one of the legs configured in the algo is OTM 20. This means that the ATM is 38300 and the OTM 20 is 40300.
Since beyond the 40000 strike, only strikes that are active occur in the multiple of 500, hence the next active strike after 40000 is 40500. But the algo will not take entries, as, based on the Leg configured, the strike selected is 40300, which is inactive.
In this case, if the option to select 500/100 multiple strikes is selected while configuring the leg, the algo will automatically take positions in the strike which is closest to 40300 but at the same time in the direction which is closer to the ATM.
Hence the algo, will take the entry in 40000 instead of shooting an order for 40300, as 40000 is the closest strike to 40300 and is also closer to the ATM than 40300 or even 40500.
HOW TO CONFIGURE THIS SETTING?
Click on the symbol selection dropdown menu > click on Legs > select the strike & select the option 500/100 multiple under Specific strike selection option. Once selected, click Done, and click Save to save the algo settings.
📣 Move SL to Cost issue for Positional trades FIXED: 📣
Earlier:
For Positional trades, if one of the sides has already Moved it's SL to Cost, the next morning, the SL of that side gets revised back to the original SL instead of SL to Cost.
After the FIX:
The next day, the SL applied will be at Cost, instead of the Original SL.
Earlier:
For Positional trades, if one of the sides has already Moved it's SL to Cost, the next morning, the SL of that side gets revised back to the original SL instead of SL to Cost.
After the FIX:
The next day, the SL applied will be at Cost, instead of the Original SL.
⚠️ IMPORTANT ⚠️
Huge spikes and slippages on the PE side today. Traders using Market orders for exits will get huge slippages. Inspite of repeat suggestions to use Limit/SL Limit orders, even some experienced traders are still using Market orders for exits in some cases.
Please use Limit/SL Limit orders for exits. Gamma spikes mostly occur on expiry days. It may be resonable to set N secs on Limit/SL Limit orders to a higher number to allow the price to cool down (ONLY for expiry days where gamma spikes are a regular occurence). A higher value like N=120 secs (for Limit/SL Limit order) may help, but comes with a risk.
Any suggestions to reduce slippages on spikes are welcome. But with suggestions, recommendations on how to address tail end risk is also required.
Huge spikes and slippages on the PE side today. Traders using Market orders for exits will get huge slippages. Inspite of repeat suggestions to use Limit/SL Limit orders, even some experienced traders are still using Market orders for exits in some cases.
Please use Limit/SL Limit orders for exits. Gamma spikes mostly occur on expiry days. It may be resonable to set N secs on Limit/SL Limit orders to a higher number to allow the price to cool down (ONLY for expiry days where gamma spikes are a regular occurence). A higher value like N=120 secs (for Limit/SL Limit order) may help, but comes with a risk.
Any suggestions to reduce slippages on spikes are welcome. But with suggestions, recommendations on how to address tail end risk is also required.
📣 New feature: Download reports / Trade Journal ⚡️
You can now export historic trade details and maintain a journal of all the trades done on Quantiply.
I. How to download reports:
Click on your profile section and go to the Reports section. Select a date or a date range and download the reports.
II. Important points:
1. Reports can be generated for a maximum of 7 days at a time.
2. Current trading day’s reports can be downloaded only after market hours, on the same day, and NOT during market hours.
3. If an algo is reset for any reason after taking positions or encountering errors, the previous trade details (in case any trades had taken place before the algo was reset) will be lost and not recorded in the reports.
4. For Positional trades, the exit trade details will show in the reports only after the trades have been squared off, till then, only the entry trades will show in the report and the exit trade details will be blank.
5. For any change in the client id/broker, algo name, or algo configuration, the latest updated client id/broker, algo name, or algo configuration will reflect in the reports, and NOT the client id/broker, algo name, or algo configuration that was used at the time and day the algo had run historically. This will be the case only for algos that were run before 30th August 2022.
For algos run after 30th August 2022, the client id/broker, algo name, or algo configuration that were used in the algo, will be the ones that will reflect in the downloaded reports, even if the client id/broker, algo name, or algo configuration is updated later.
You can now export historic trade details and maintain a journal of all the trades done on Quantiply.
I. How to download reports:
Click on your profile section and go to the Reports section. Select a date or a date range and download the reports.
II. Important points:
1. Reports can be generated for a maximum of 7 days at a time.
2. Current trading day’s reports can be downloaded only after market hours, on the same day, and NOT during market hours.
3. If an algo is reset for any reason after taking positions or encountering errors, the previous trade details (in case any trades had taken place before the algo was reset) will be lost and not recorded in the reports.
4. For Positional trades, the exit trade details will show in the reports only after the trades have been squared off, till then, only the entry trades will show in the report and the exit trade details will be blank.
5. For any change in the client id/broker, algo name, or algo configuration, the latest updated client id/broker, algo name, or algo configuration will reflect in the reports, and NOT the client id/broker, algo name, or algo configuration that was used at the time and day the algo had run historically. This will be the case only for algos that were run before 30th August 2022.
For algos run after 30th August 2022, the client id/broker, algo name, or algo configuration that were used in the algo, will be the ones that will reflect in the downloaded reports, even if the client id/broker, algo name, or algo configuration is updated later.