Quantiply.tech

⚠️ Upstox broker login/token generation failing. Issue raised with Upstox⚠️

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

📣 FEATURE UPDATE 📣 Re-entry with Wait & Trade 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

📣 FEATURE UPDATE 📣 Re-entry with Wait & Trade If Wait & trade is selected, then after hitting the SL, the leg will re-enter only if the Wait & Trade condition is fulfilled.

📣 ANNOUCEMENT 📣 Live support will be unavailable between 1 PM to 2 PM today

⚠️ZERODHA throwing a lot of errors for order placement⚠️ ERROR -:NetworkException:No response from server with error code: ECONNABORTED Lot of orders not been placed inspite of re-tries. Check your algos and terminals if you are using ZERODHA

📣 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

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

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

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

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

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

⚠️AngelOne access token generation (broker login) failing for all users. Seems like it should start working around 8:30AM like yesterday⚠️

⚠️AngelOne users can reset the password for the login to work. With password reset it will work. Since you may have tried to broker login multiple times, the account would have got blocked. To unblock and broker login successfully, you would need to reset the AngelOne trading account password⚠️

⚠️AngelOne access token generation (broker login) failing for all users. Issue has been raised with AngelOne⚠️

⚠️AngelOne access token (broker login) issue RESOLVED! ⚠️

⚠️AngelOne access token generation (broker login) failing for all users. Issue has been raised with AngelOne⚠️

⚠️ ANNOUCEMENT ⚠️ Today, we had a sudden, unexpected increase in the number of algos deployed by users, so one of the servers bore the brunt & algos running on that server shut down. About 7-10% of the all algos running on Quantiply were affected. We have added additional servers already to mitigate the risk of it occurring again tomorrow or day after. Some ongoing scaling & optimisation activity once completed will also greatly minimise the risk of this issue happening in the future. We would need 2-3 days more to completely address this issue.