⚠️All positional users need to make sure that broker login is done before 8:55 AM. The positional algos from previous days will not work if broker login not done before 8:55 AM⚠️

⚠️ Lower premium selection: ⚠️

Please note that for NIFTY and BANKNIFTY, you might not get extremely low premiums, like for example if your setting is premium<6 for Nifty, as the last available strike which is 14750PE has a premium of ~8, the algo will not be taking positions as the condition of premium <6 is not fulfilled

Solution: Keep premium based entries settings something like premium > 6 ie. premium more than 6, so that it can take the next best strike with premium closest to but higher than 6

Please note the available symbols for Nifty and Banknifty for today on Quantiply:

BANKNIFTY:
33400CE - 42400CE
30900PE - 39400PE

NIFTY:
15150CE - 19650CE
14750PE - 18150PE

The algos will and can read prices and take positions only for the above symbols, so best to keep premium based entry settings as ‘premium higher than’ instead of ‘premiums lower than’ for days with higher premiums like Fridays and Mondays

⚠️ For errors related to price outside circuit limit, place SL orders manually ⚠️

This error will keep coming till circuit limits are not updated at the exchange. This error can also come for Positional algos where next morning one of the side's premium has decayed substantially and the SL order being placed by the algo based on the previous day's SL setting is outside circuit limit. A solution is to reduce SL settings so that the SL price is within circuit limits shown in the error message.

To modify SL settings, you will have to remove the SL completely and make it none (for the leg that is giving the error), and again modify the SL settings with SL in % or Points much closer

⚠️ Announcement from IIFL: All IIFL users, please delete old version of your XTS mobile app and install the updated one shared below:

https://workdrive.zohoexternal.com/file/cxgb2fb0a15ae891e480994913f80f4f1f134

iOS app link will be shared later today

⚠️ Announcement from IIFL: All IIFL users, please delete old version of your XTS mobile app and install the updated one shared below:

iOS: https://testflight.apple.com/join/VOssI4bd

DUPLICATE OR DELETE MULTIPLE ALGOS:

You can now duplicate or delete multiple algos at the same time.

NOTES:

For duplicating multiple algos:
1. Add text before or after the algo name. This text can be useful to differentiate between existing algos and duplicated algos. It can come very handy when you are duplicating algos temporarily to another day, for example, when Wednesday is an expiry day, if Thursday is a trading holiday. Add text setting can also be left empty while duplicating multiple algos.
2. Duplicate multiple algos to a specific day or multiple days at the same time.
3. Select client ID/broker: If you select a client ID/broker while duplicating multiple algos, all the duplicated algos will have that selected client ID/broker applied. If you DO NOT select a client ID/broker while duplicating multiple algos, then the existing client ID/broker selection, if any, will get applied to the duplicated algos.

For deleting multiple algos:
1. Unlike earlier, you can now delete disabled algos during market hours.
2. Algos cannot be deleted when they’re in the following state during market hours: Trade Active, Trade Closed, Ready. You can delete only Disabled or Enabled algo(s) during market hours. If an algo is in Ready status, you can disabled it and then delete.

Main use cases for this feature:
1. Thursday is a trading holiday, and you want to trade all your expiry day strategies on Wednesday. In this case, the Thursday algos (strategies) will have to be duplicated to Wednesday, and then these duplicated algos can be deleted after market hours on Wednesday.
2. You’ve added a new client id to your Quantiply account, and need to duplicate & run all the same algos (strategies) being traded on another client ID/broker.

Tips:
1. Use the search filter to narrow down on multiple algos you want to duplicate or delete.
2. Use the Select all filter to filter algos by statuses.
3. Group algos by renaming it with a common text, so it can be easily filtered using Search. Eg. Add client ids, day, or strategy name or type as additional text in algo names.

🔔 NEW FEATURE ANNOUNCEMENT 📣

RE-ENTRY

This feature allows the re-entry of positions that have exited upon hitting the Stoploss.

RELEASE NOTES
(⚠️Check your email for examples with images⚠️):

I. Re-entry types:

1. RE COST (Re-entry at Cost ie. re-entry at original average entry price):
After the SL hits, if the price comes back to the original average entry price, the algo will re-enter the same leg/symbol. If the original position was a Sell, then the re-entered position will also be a Sell. The same SL or Target settings will get applied upon re-entry.

Example: A PE Strike was sold at 200 premium with SL setting 10%, ie. SL price 220. If the SL hits, the algo exits the leg at 220. If the price were to come back to the average entry price of 200, the algo would re-enter the same strike/symbol ie. a Sell position would be taken in the same strike/symbol.

2. RE COST REVERSE (Re-entry at cost but reverse position):
After the SL hits, if the price comes back to the original average entry price, the algo will re-enter the same leg/symbol but in REVERSE. ie. If the original trade was a Sell, then the re-entered leg will be a Buy. The same SL or Target settings will get applied upon re-entry. If this re-entered buy leg were to hit SL, and price were to come back to the average entry price, then the algo will again re-enter but in Reverse ie. the re-entered leg will be a Sell. For this type of re-entry, the leg will keep alternating between Sell & Buy every time it re-enters.

Example: A PE Strike was sold at 200 premium with SL setting 10%, ie. SL price 220. If the SL hits, the algo exits the leg at 220. If the price were to come back to the average entry price of 200, the algo would re-enter the same strike/symbol but it would reverse the direction ie. instead of Selling the same strike/symbol, the algo would Buy the same strike/symbol.

3. RE ASAP (Immediate re-entry if the SL is hit):
As soon as the SL is hit, the algo will re-enter. If the strike level changes as per the leg setting, the latest strike will be selected for re-entry. In this case, if the original leg was a Sell, then the re-entered leg will also be a Sell. The same SL or Target settings will get applied upon re-entry.

Example: An ATM strike of 37400 CE was sold at 200 premium with SL setting 30%, ie. SL price 260. If the SL hits, the algo exits the leg at 260, and the algo immediately checks the latest ATM based on the underlying, in this case the underlying’s price was 37460, then the ATM strike of 37500 CE is selected and a new Sell position is taken in 37500 CE.

4. RE ASAP REVERSE (Immediate re-entry if the SL is hit, but reverse the position):
As soon as the SL is hit, the algo will re-enter but in reverse. If the strike level changes as per the leg setting, the latest strike will be selected for re-entry. In this case, if the original leg was a Sell, then the re-entered leg will be a Buy. The same SL or Target settings will get applied upon re-entry. For this type of re-entry, the leg will keep alternating between Sell & Buy, every time it re-enters.

Example: An ATM strike of 37400 CE was sold at 200 premium with SL setting 30%, ie. SL price 260. If the SL hits, the algo exits the leg at 260, and the algo immediately checks the latest ATM based on the underlying, in this case the underlying’s price was 37460, then the ATM strike of 37500 CE is selected and instead of Selling the leg, it will reverse the direction and take a Buy position in 37500 CE.

5. MTM RE-ENTRY - Square off & re-enter (Re-enter 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. 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.

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.

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.

⚠️ 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.

⚠️ 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.

📣 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.

📣 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

📣 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

📣 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)

📣 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.

📣 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.

📣 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