📣 ANNOUCEMENT 📣
Live support will be unavailable between 1 PM to 2 PM today
Live support will be unavailable between 1 PM to 2 PM today
📣 FEATURE UPDATE 📣
Re-entry with Wait & Trade - (RE-EXECUTE as per STOCKMOCK)
If Wait & trade is selected, then after hitting the SL, the leg will re-enter only if the Wait & Trade condition is fulfilled.
1. Re-entry with Wait & Trade (RE W&T):
Example:
Start time: 9:20
Wait & Trade setting: Up 50%
Stoploss: 10%
Leg setting: ATM Buy
At 9:20 a strike is selected based on the spot price, the LTP of that strike is 100 (100 becomes the reference price), the leg enters the buy trade when price reaches 150 based on the W&T and leg setting. The calculated Stoploss is 135. Once the SL hit of 135 is hit, the spot price at the time of Stoploss hit will define the latest ATM strike and also record the new reference price which would be the LTP of the strike at the time of SL hit. Say the reference price of the latest ATM strike is 60. Based on the wait & trade setting, a re-entry will happen in the new ATM strike once the price goes from 60 to 90. The leg will enter at 90 and have a stoploss of 81
2. Reverse Re-entry with Wait & Trade (RE W&T REVERSE)
The logic will be the same. The difference would be that the re-entry order would be a sell order instead of buy.
Other important points:
- If you use Wait & Trade with Immediate settings, it will act like re-entry type - RE-ASAP
- If Wait & Trade setting is selected, the Re-entry type for each individual leg has to be compulsorily RE W&T and RE W&T REVERSE, none of the other 4 can be selected.
- In the case of Premium based entries ie. premium close to, at the time the first SL is hit, a strike will be selected again with based on the configured premium, and the algo will wait for the wait & trade condition to be fulfilled to trigger the entry
Re-entry with Wait & Trade - (RE-EXECUTE as per STOCKMOCK)
If Wait & trade is selected, then after hitting the SL, the leg will re-enter only if the Wait & Trade condition is fulfilled.
1. Re-entry with Wait & Trade (RE W&T):
Example:
Start time: 9:20
Wait & Trade setting: Up 50%
Stoploss: 10%
Leg setting: ATM Buy
At 9:20 a strike is selected based on the spot price, the LTP of that strike is 100 (100 becomes the reference price), the leg enters the buy trade when price reaches 150 based on the W&T and leg setting. The calculated Stoploss is 135. Once the SL hit of 135 is hit, the spot price at the time of Stoploss hit will define the latest ATM strike and also record the new reference price which would be the LTP of the strike at the time of SL hit. Say the reference price of the latest ATM strike is 60. Based on the wait & trade setting, a re-entry will happen in the new ATM strike once the price goes from 60 to 90. The leg will enter at 90 and have a stoploss of 81
2. Reverse Re-entry with Wait & Trade (RE W&T REVERSE)
The logic will be the same. The difference would be that the re-entry order would be a sell order instead of buy.
Other important points:
- If you use Wait & Trade with Immediate settings, it will act like re-entry type - RE-ASAP
- If Wait & Trade setting is selected, the Re-entry type for each individual leg has to be compulsorily RE W&T and RE W&T REVERSE, none of the other 4 can be selected.
- In the case of Premium based entries ie. premium close to, at the time the first SL is hit, a strike will be selected again with based on the configured premium, and the algo will wait for the wait & trade condition to be fulfilled to trigger the entry
Wait & Trade with Re-entry on Quantiply currently works as Wait & Trade + ReExecute as present on Stockmock.
We will be releasing the Wait & Trade with Re-entry at Cost functionality on Tuesday 7th June after testing.
We will be releasing the Wait & Trade with Re-entry at Cost functionality on Tuesday 7th June after testing.
📣 FEATURE UPDATE 📣
Wait & Trade with Re-entry at Cost (W&T + RE COST)
1. Wait & Trade with Re-entry at Cost (W&T + RE COST):
Example:
Start time: 9:20
Wait & Trade setting: Up 10 points
Stoploss: 10%
Leg setting: ATM Buy
At 9:20 the ATM strike is selected based on the spot price, the LTP of that strike is 100 (100 becomes the reference price ie. the price captured at the start time for that strike), the leg enters the buy trade when price reaches 110 based on the W&T and leg setting. The calculated Stoploss is 99. The leg exits if the SL of 99 is hit. After SL is hit, IF the price goes back to 110 (which is the original entry price) the algo will re-enter that leg ie. the same strike. In this case since Re-entry at Cost is selected, the strike price will be the same for all re-entries. The same process is repeated for the number of times re-entry is configured.
2. Wait & Trade with Reverse Re-entry at Cost (W&T + REVERSE RE COST):
The logic will be the same. The difference would be that the re-entry order would be a sell order instead of buy and it would keep alternating for all the re-entries that follow
Note:
- The re-entry price will always be considered as the original entry price which is calculated from the reference price, and NOT the average entry price of the first original trade.
Wait & Trade with Re-entry at Cost (W&T + RE COST)
1. Wait & Trade with Re-entry at Cost (W&T + RE COST):
Example:
Start time: 9:20
Wait & Trade setting: Up 10 points
Stoploss: 10%
Leg setting: ATM Buy
At 9:20 the ATM strike is selected based on the spot price, the LTP of that strike is 100 (100 becomes the reference price ie. the price captured at the start time for that strike), the leg enters the buy trade when price reaches 110 based on the W&T and leg setting. The calculated Stoploss is 99. The leg exits if the SL of 99 is hit. After SL is hit, IF the price goes back to 110 (which is the original entry price) the algo will re-enter that leg ie. the same strike. In this case since Re-entry at Cost is selected, the strike price will be the same for all re-entries. The same process is repeated for the number of times re-entry is configured.
2. Wait & Trade with Reverse Re-entry at Cost (W&T + REVERSE RE COST):
The logic will be the same. The difference would be that the re-entry order would be a sell order instead of buy and it would keep alternating for all the re-entries that follow
Note:
- The re-entry price will always be considered as the original entry price which is calculated from the reference price, and NOT the average entry price of the first original trade.
⚠️ ANNOUCEMENT ⚠️
For POSITIONAL algos with MOVE SL TO COST selected, the SL doesn't move to cost the next day after check condition next day (time).
This logic will be modified so that it can Move SL to Cost the next day as well after check condition next day (time), if on the previous day the SL was already hit. Till this logic is changed in the system you can use a temporary workaround shared below.
Workaround: After Check condition next day after time, you can click Modify Settings, remove Move SL to Cost selection, then click Save, then again click Modify Settings, select Move SL to Cost and click Save Settings.
Note: this is only applicable for Positional algos which have Move SL to Cost selected and SLs are hit the previous day itself.
For POSITIONAL algos with MOVE SL TO COST selected, the SL doesn't move to cost the next day after check condition next day (time).
This logic will be modified so that it can Move SL to Cost the next day as well after check condition next day (time), if on the previous day the SL was already hit. Till this logic is changed in the system you can use a temporary workaround shared below.
Workaround: After Check condition next day after time, you can click Modify Settings, remove Move SL to Cost selection, then click Save, then again click Modify Settings, select Move SL to Cost and click Save Settings.
Note: this is only applicable for Positional algos which have Move SL to Cost selected and SLs are hit the previous day itself.
⚠️ Announcement from IIFL: All IIFL users, please delete old version of your XTS mobile app on your iOS (Apple) devices and install the updated one:
iOS app: https://testflight.apple.com/join/VOssI4bd
Note: Android apps will get updated automatically⚠️
iOS app: https://testflight.apple.com/join/VOssI4bd
Note: Android apps will get updated automatically⚠️
📣 FEATURE UPDATES 📣
2 new features:
1. Clientwise Stoploss & Target (Global Stoploss & Target).
2. Square off individual legs with multi-select option.
2 new features:
1. Clientwise Stoploss & Target (Global Stoploss & Target).
2. Square off individual legs with multi-select option.
This media is not supported in your browser
VIEW IN TELEGRAM
New feature: Client wise Stoploss & Target
This functionality enables the exit of all algos (strategies) running on a particular Client ID at once, upon hitting the portfolio-level Stoploss or Target as set by the user.
This functionality enables the exit of all algos (strategies) running on a particular Client ID at once, upon hitting the portfolio-level Stoploss or Target as set by the user.
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 ⚠️