Example: An Iron Condor is sold with the following positions, Sell 37400 CE, Sell 37400 PE, Buy 37500 CE, Buy 37300 PE with an SL set to Rs. 2000. If the SL hits, the algo will select the latest strikes as per the legs configured in the settings and the underlying, and immediately re-enter the Iron Condor. Based on the underlying price and legs configured, the strikes re-entered may or may not be the same.
6. MTM REVERSE RE-ENTRY - Square off, reverse positions & re-enter (Re-enter reverse positions if the combined premium SL (or MTM SL) is hit:
When the MTM SL hits, the algo will immediately square off all legs and open new positions in all the legs but in reverse. If the original positions were a Sell, then the re-entered positions would be Buy. For this type of re-entry, the legs will keep alternating between Sell & Buy, every time it re-enters. It is possible that the strike prices change or stay the same, based on the latest price of the underlying and the leg configuration settings.
II. Other Settings:
1. Number of times re-entry setting:
<Check your email for the image>
With this setting, you can define the maximum number of times re-entry should happen. You can individually define max no. of re-entries for each individual leg and MTM re-entries.
If a value of ‘2’ is given for this setting, it will mean that the position will be taken a total of 3 times, ie. (1 x original entry) + (2 x re-entries).
A maximum of 20 re-entries is allowed, if a max limit were to be set. But, if “No max limit’ setting is selected, the algo will re-enter any number of times, the re-entry condition is fulfilled.
Refer to the image below. <Check your email for the image>. Let’s look at an example where Individual leg re-entries and MTM SL re-entries, both, are configured in an algo, let’s see the example of CE leg which is sold, in this case, 39400 CE, which has been given a maximum number of re-entries setting of 2.
Here, upon taking positions, the 39400 CE leg hit SL, and re-entered once. That will be considered as re-entry 1. Later, MTM SL got hit and MTM re-entry condition was fulfilled due to which all original positions were squared off and a re-entry happened in all legs. This MTM re-entry will not be considered a re-entry for the individual leg 39400 CE which had a setting of maximum 2 re-entries.
A little later, 39400 CE’s individual SL is hit, and a re-entry condition is fulfilled and it re-enters. This individual re-entry of 39400 CE will be considered the 2nd re-entry, post which if SL were to hit, then a 3rd re-entry will not take place for this individual leg. But in case if MTM SL Re-entry had a maximum number of times re-entry of 2, then all the legs including 39400 CE will re-enter as an MTM re-entry along with the other legs. In short, MTM SL re-entry does not include or count an individual re-entry.
2. Re-entry time settings:
a. Re-entry only after (time):
In the above example, re-entry will take place only after 11:15:05. Even if the Re-entry condition is fulfilled before 11:15:05, the algo will not re-enter. If SL is hit before 11:15:05, then the position will be closed for the whole day, the leg will not re-enter even after 11:15:05.
b. Re-entry only before (time):
In the above example, re-entry will take place only before 14:30:00. Even if the Re-entry condition is fulfilled after 14:30:00, the algo will not re-enter. If the SL is hit after 14:30:00, and the re-entry conditions are fulfilled, even then the leg(s) will not re-enter.
c. Re-entry between (time):
In the above example, re-entry will take place only between 11:15:05 and 14:30:00. If the SL is hit before 11:15:05 or after 14:30:00, the positions will be closed for the day. Even if the SL hits between the above set time, but the re-entry condition is fulfilled before 11:15:05 or after 14:30:00, the algo will not re-enter positions.
6. MTM REVERSE RE-ENTRY - Square off, reverse positions & re-enter (Re-enter reverse positions if the combined premium SL (or MTM SL) is hit:
When the MTM SL hits, the algo will immediately square off all legs and open new positions in all the legs but in reverse. If the original positions were a Sell, then the re-entered positions would be Buy. For this type of re-entry, the legs will keep alternating between Sell & Buy, every time it re-enters. It is possible that the strike prices change or stay the same, based on the latest price of the underlying and the leg configuration settings.
II. Other Settings:
1. Number of times re-entry setting:
<Check your email for the image>
With this setting, you can define the maximum number of times re-entry should happen. You can individually define max no. of re-entries for each individual leg and MTM re-entries.
If a value of ‘2’ is given for this setting, it will mean that the position will be taken a total of 3 times, ie. (1 x original entry) + (2 x re-entries).
A maximum of 20 re-entries is allowed, if a max limit were to be set. But, if “No max limit’ setting is selected, the algo will re-enter any number of times, the re-entry condition is fulfilled.
Refer to the image below. <Check your email for the image>. Let’s look at an example where Individual leg re-entries and MTM SL re-entries, both, are configured in an algo, let’s see the example of CE leg which is sold, in this case, 39400 CE, which has been given a maximum number of re-entries setting of 2.
Here, upon taking positions, the 39400 CE leg hit SL, and re-entered once. That will be considered as re-entry 1. Later, MTM SL got hit and MTM re-entry condition was fulfilled due to which all original positions were squared off and a re-entry happened in all legs. This MTM re-entry will not be considered a re-entry for the individual leg 39400 CE which had a setting of maximum 2 re-entries.
A little later, 39400 CE’s individual SL is hit, and a re-entry condition is fulfilled and it re-enters. This individual re-entry of 39400 CE will be considered the 2nd re-entry, post which if SL were to hit, then a 3rd re-entry will not take place for this individual leg. But in case if MTM SL Re-entry had a maximum number of times re-entry of 2, then all the legs including 39400 CE will re-enter as an MTM re-entry along with the other legs. In short, MTM SL re-entry does not include or count an individual re-entry.
2. Re-entry time settings:
a. Re-entry only after (time):
In the above example, re-entry will take place only after 11:15:05. Even if the Re-entry condition is fulfilled before 11:15:05, the algo will not re-enter. If SL is hit before 11:15:05, then the position will be closed for the whole day, the leg will not re-enter even after 11:15:05.
b. Re-entry only before (time):
In the above example, re-entry will take place only before 14:30:00. Even if the Re-entry condition is fulfilled after 14:30:00, the algo will not re-enter. If the SL is hit after 14:30:00, and the re-entry conditions are fulfilled, even then the leg(s) will not re-enter.
c. Re-entry between (time):
In the above example, re-entry will take place only between 11:15:05 and 14:30:00. If the SL is hit before 11:15:05 or after 14:30:00, the positions will be closed for the day. Even if the SL hits between the above set time, but the re-entry condition is fulfilled before 11:15:05 or after 14:30:00, the algo will not re-enter positions.
Points to remember (Re-entry feature):
1. Once the trade is active Re-entry type setting cannot be modified, but, maximum number of re-entries setting, can be modified.
2. For MTM SL, the values set in the MTM SL section will be considered as SL, if this SL is hit, then the re-entry condition will be checked. If you want your max loss in a strategy to be 6000 only, then you can set the SL value and no. of re-entries accordingly. In the below (Image) example, if SL value is set to 2000 and max re-entries is set to 2, it means the (1 x original entry) + (2 x re-entries) may make up for a max loss of 6000, after which the algo will completely exit and close the entire trade. Refer image below:
<Check your email for the image>
3. Re-entry orders will be fired ONLY when re-entry condition is fulfilled, even if Entry/Exit order type is Limit/SL-Limit. The algo will not place re-entry Limit/SL-Limit orders right after the original or previous SL is hit.
4. The re-entry feature can work along with Move SL to Cost feature.
5. The Re-entry feature cannot work along with the Wait & Trade feature in this release. In the next release Wait & Trade will be enabled to work with the Re-entry feature.
6. Once the positions are taken by the algo, you can see that each leg is color coded with a color strip in the Status column. This color coding helps differentiate between unique open positions and the positions re-entered.
1. Once the trade is active Re-entry type setting cannot be modified, but, maximum number of re-entries setting, can be modified.
2. For MTM SL, the values set in the MTM SL section will be considered as SL, if this SL is hit, then the re-entry condition will be checked. If you want your max loss in a strategy to be 6000 only, then you can set the SL value and no. of re-entries accordingly. In the below (Image) example, if SL value is set to 2000 and max re-entries is set to 2, it means the (1 x original entry) + (2 x re-entries) may make up for a max loss of 6000, after which the algo will completely exit and close the entire trade. Refer image below:
<Check your email for the image>
3. Re-entry orders will be fired ONLY when re-entry condition is fulfilled, even if Entry/Exit order type is Limit/SL-Limit. The algo will not place re-entry Limit/SL-Limit orders right after the original or previous SL is hit.
4. The re-entry feature can work along with Move SL to Cost feature.
5. The Re-entry feature cannot work along with the Wait & Trade feature in this release. In the next release Wait & Trade will be enabled to work with the Re-entry feature.
6. Once the positions are taken by the algo, you can see that each leg is color coded with a color strip in the Status column. This color coding helps differentiate between unique open positions and the positions re-entered.
⚠️ Functionality Update ⚠️
Move SL to Cost can now be used along with Wait & Trade
Move SL to Cost works only when 2 opposite side legs are open simultaneously. When 1 side SL hits, the leg(s) of the other side will have their stoplosses moved to cost.
In the case of Wait & Trade, if only one leg is open, and it’s SL hits, and later if the other side leg also enters, the SL that gets applied will be it’s original SL as configured in the settings.
In short, SL’s can be moved to cost only when 2 opposite side legs are open simultaneously and one side hits the SL.
Move SL to Cost can now be used along with Wait & Trade
Move SL to Cost works only when 2 opposite side legs are open simultaneously. When 1 side SL hits, the leg(s) of the other side will have their stoplosses moved to cost.
In the case of Wait & Trade, if only one leg is open, and it’s SL hits, and later if the other side leg also enters, the SL that gets applied will be it’s original SL as configured in the settings.
In short, SL’s can be moved to cost only when 2 opposite side legs are open simultaneously and one side hits the SL.
⚠️ UI Update ⚠️
Algo running / not running status added to the main page (marked with light green arrows in the image)
Dot should be red when algo is in the following status:
1. Disabled
2. Enabled
3. Trade Closed
Dot should be green when algo is in the following status:
1. Ready
2. Trade Active
If the dot is red when the algo is in Ready or Trade Active status, then the algo is not running when it's supposed to be and can be highlighted to @abhishah33.
Algo running / not running status added to the main page (marked with light green arrows in the image)
Dot should be red when algo is in the following status:
1. Disabled
2. Enabled
3. Trade Closed
Dot should be green when algo is in the following status:
1. Ready
2. Trade Active
If the dot is red when the algo is in Ready or Trade Active status, then the algo is not running when it's supposed to be and can be highlighted to @abhishah33.
📣 ANNOUNCEMENT 📣
Re-entry logic update for Re-cost with Trailing SL
[This logic change is specific only to a scenario where re-cost type re-entry and trailing SL are both enabled together]
New logic:
If the SL of a leg trails and goes into profit, upon hitting the trailed SL, re-entry will not happen till the price goes back to the original entry price (even if the current price is below the sell entry price or the current price is above the buy entry price).
Old logic:
If the SL of a leg trails, goes into profit and then hits the trailing SL, re-entry will happen immediately as the current price is below the sell entry price or the current price is above the buy entry price.
Re-entry logic update for Re-cost with Trailing SL
[This logic change is specific only to a scenario where re-cost type re-entry and trailing SL are both enabled together]
New logic:
If the SL of a leg trails and goes into profit, upon hitting the trailed SL, re-entry will not happen till the price goes back to the original entry price (even if the current price is below the sell entry price or the current price is above the buy entry price).
Old logic:
If the SL of a leg trails, goes into profit and then hits the trailing SL, re-entry will happen immediately as the current price is below the sell entry price or the current price is above the buy entry price.
📣 ANNOUNCEMENT 📣
RE-ENTRY feature - Functionality Update
Addition of a new setting - 'Re-entry type', applicable for all 4 types of re-entry, (ie. Re-Cost, Re-Cost reverse, Re-Asap, Re-Asap reverse)
1. LTP: If this option is selected, after SL is hit, the re-entry will be triggered as soon as the LTP reaches the average entry price in the case of Re-Cost and re-entry will be triggered immediately in the case of Re-Asap. This is the current default logic
2. Candle Close: If this option is selected, after SL is hit, the algo will check if the LTP is at or below the sell entry price and at or above buying price at the end of every minute (or candle close). If this condition is fulfilled, then the re-entry will be triggered. And in the case of Re-entry Asap, after the SL is hit, the re-entry will be triggered at the end of the minute (or at candle close).
The candle close logic of re-entry is based on the Stockmock's re-entry logic. Use the candle close option if you want to follow Stockmock's re-entry log
RE-ENTRY feature - Functionality Update
Addition of a new setting - 'Re-entry type', applicable for all 4 types of re-entry, (ie. Re-Cost, Re-Cost reverse, Re-Asap, Re-Asap reverse)
1. LTP: If this option is selected, after SL is hit, the re-entry will be triggered as soon as the LTP reaches the average entry price in the case of Re-Cost and re-entry will be triggered immediately in the case of Re-Asap. This is the current default logic
2. Candle Close: If this option is selected, after SL is hit, the algo will check if the LTP is at or below the sell entry price and at or above buying price at the end of every minute (or candle close). If this condition is fulfilled, then the re-entry will be triggered. And in the case of Re-entry Asap, after the SL is hit, the re-entry will be triggered at the end of the minute (or at candle close).
The candle close logic of re-entry is based on the Stockmock's re-entry logic. Use the candle close option if you want to follow Stockmock's re-entry log
📣 ANNOUNCEMENT 📣
Bulk action: Square off & Terminate / Terminate buttons for multiple algos.
You can now Square off & terminate OR Terminate, multiple algos at the same time, with a single click.
These buttons will be visible only when one or more of the selected algos are in 'Trade Active' status.
Edit: You can also use the Search filter or the sorting filters, to filter out specific algos by algo name, client id, broker name, MTM, algo status etc, and then Square Off & terminate or Terminate those specific algos. Other active algos will not get terminated if search or sort filters are used to narrow down on specific algos
Bulk action: Square off & Terminate / Terminate buttons for multiple algos.
You can now Square off & terminate OR Terminate, multiple algos at the same time, with a single click.
These buttons will be visible only when one or more of the selected algos are in 'Trade Active' status.
Edit: You can also use the Search filter or the sorting filters, to filter out specific algos by algo name, client id, broker name, MTM, algo status etc, and then Square Off & terminate or Terminate those specific algos. Other active algos will not get terminated if search or sort filters are used to narrow down on specific algos
📣 FEATURE UPDATE 📣
Option to calculate entry and exit from Average Entry/Exit Price OR LTP
(This setting can be found under the Advanced Settings option on the algo config page)
1. Calculate entry from:
(A) Average Entry Price (default):
The algo will calculate all targets & stoplosses from the average entry price (ie. the average execution price for the whole quantity). This is the current default mechanism that all algos use.
(B) LTP:
The algo will calculate all targets & stoplosses from the LTP recorded at the time when the order was fully filled or executed.
Example: At 9:20:00 the price of a CE strike is 100, the algo fires an order in this CE strike at 09:20:00, the order was successfully filled at 09:20:01 @ 98, the LTP of the CE strike at 09:20:01 was 99. In this case, if option (A) - Average Entry Price is selected, then the algo will calculate Targets & SLs from 98. If option (B) - LTP was selected then the algo will calculate Targets & SLs from 99, as 99 was the LTP at the time the order was successfully filled
In the case of Wait & Trade, if option (B) - LTP is selected, then the algo will calculate all targets & stoplosses from the Entry price, which is derived from the Reference price. In all other cases, it will consider the LTP from the time the order was fully filled or executed.
1. Calculate exit from:
(A) Average Exit Price (default):
The algo will consider the exit price as the average exit price (ie.the average execution price for the whole quantity). This is the current default mechanism that all algos use.
(B) LTP:
The algo will consider the exit price as the LTP that was recorded at the time the exit order got fully filled or executed.
Example: At 15:15:00 the price of a CE strike is 20, the algo fires a the square off order in this CE strike at 15:15:00, the order was successfully filled at 15:15:02 @ 21, the LTP of the CE strike at 15:15:02 was 20.5. In this case, if option (A) - Average Exit Price is selected, then the algo will consider the exit price as 21. If option (B) - LTP was selected then the algo will consider the exit price as 20.5, as the LTP at the time the order got executed at 15:15:02 was 20.5.
Option to calculate entry and exit from Average Entry/Exit Price OR LTP
(This setting can be found under the Advanced Settings option on the algo config page)
1. Calculate entry from:
(A) Average Entry Price (default):
The algo will calculate all targets & stoplosses from the average entry price (ie. the average execution price for the whole quantity). This is the current default mechanism that all algos use.
(B) LTP:
The algo will calculate all targets & stoplosses from the LTP recorded at the time when the order was fully filled or executed.
Example: At 9:20:00 the price of a CE strike is 100, the algo fires an order in this CE strike at 09:20:00, the order was successfully filled at 09:20:01 @ 98, the LTP of the CE strike at 09:20:01 was 99. In this case, if option (A) - Average Entry Price is selected, then the algo will calculate Targets & SLs from 98. If option (B) - LTP was selected then the algo will calculate Targets & SLs from 99, as 99 was the LTP at the time the order was successfully filled
In the case of Wait & Trade, if option (B) - LTP is selected, then the algo will calculate all targets & stoplosses from the Entry price, which is derived from the Reference price. In all other cases, it will consider the LTP from the time the order was fully filled or executed.
1. Calculate exit from:
(A) Average Exit Price (default):
The algo will consider the exit price as the average exit price (ie.the average execution price for the whole quantity). This is the current default mechanism that all algos use.
(B) LTP:
The algo will consider the exit price as the LTP that was recorded at the time the exit order got fully filled or executed.
Example: At 15:15:00 the price of a CE strike is 20, the algo fires a the square off order in this CE strike at 15:15:00, the order was successfully filled at 15:15:02 @ 21, the LTP of the CE strike at 15:15:02 was 20.5. In this case, if option (A) - Average Exit Price is selected, then the algo will consider the exit price as 21. If option (B) - LTP was selected then the algo will consider the exit price as 20.5, as the LTP at the time the order got executed at 15:15:02 was 20.5.
📣 ANNOUCEMENT 📣
Refrain from using Calculate entry from: LTP setting and premium based entries (ie. entry by specific premium) together. We’re modifying the logic to handle an edge case. Once the logic is modified, we will make an announcement and you can then resume using these 2 functionalities together. It will be available to use today or tomorrow.
Refrain from using Calculate entry from: LTP setting and premium based entries (ie. entry by specific premium) together. We’re modifying the logic to handle an edge case. Once the logic is modified, we will make an announcement and you can then resume using these 2 functionalities together. It will be available to use today or tomorrow.
📣 ANNOUCEMENT 📣
Calculate entry from: LTP setting and premium based entries (ie. entry by specific premium) can now be configured and used together. Logic has been modified to handle an edge case
Calculate entry from: LTP setting and premium based entries (ie. entry by specific premium) can now be configured and used together. Logic has been modified to handle an edge case
📣 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.