Quantiply.tech

⚠️ ❗️For users using the PLACE IN ADVANCE option for SL orders ❗️⚠️ Some of the BANKNIFTY strikes on the PE side like 41500PE, 41400PE, 41300PE etc would be giving a circuit limit error while placing SL orders. If you have got this error, you will have to try and place the SL order manually or manage the position manually. Inspite of multiple retries by the algo, the SL orders has still been giving this circuit limit error as it seems that the circuit limits had not been updated at the exchange. This error may or may not come for the upcoming algos as the range would have been extended by the exchange by that time.

📣 Run THURSDAY algos on WEDNESDAY📣 Here's a video on how to run your Thursday algos on Wednesday, as the upcoming Thursday 26th Jan is a trading holiday (Republic Day) and Wednesday 25th is the Expiry day

⚠️ ❗️ALL users ❗️⚠️ Some updates are being pushed. The website will be unavailable for sometime

⚠️ ❗️FINVASIA users ❗️⚠️ Finvasia issue resolved ✅ Please be careful and monitor if you are going to take new trades now. Old open positions without any error should exit/re-enter/square off properly

⚠️ ❗️FINVASIA users ❗️⚠️ If any algo is scheduled to run in the coming minutes, please disable the algos and do not take any fresh positions till there is a confirmation from Finvasia that the issue is resolved. Disable all new algos for the day

⚠️ ❗️FINVASIA users ❗️⚠️ While we wait for the issue to get resolved, Finvasia users who have got errors for taking fresh positions, can share the algo page links with @abhishah33 so that the algos can be reset and re-used again. Once the algo is reset, and only once the issue is resolved, one can disable the algo, and enable the algo again, and the algo will go into READY status and take fresh positions again. Those whose algos are already running will have to manually exit the positions that have given the error

⚠️ ❗️FINVASIA users ❗️⚠️ Finvasia users would be getting an error SAF:Yel is down for order placement. We have notified Finvasia about this. We will update once the issue is resolved. Please execute and manage positions manually for now

⚠️ ❗️ALL users ❗️⚠️ The platform will be down for the next 2 hours, from 11:30 PM to 1:30 AM for a system upgrade. Quantiply web application will not be available for the next 2 hours temporarily.

⚠️ ❗️ALL users ❗️⚠️ Live support on chat will be unavailable from 11 AM to 1:30 PM today

⚠️ ❗️ALL users ❗️⚠️ Any changes made to algos yesterday after 4:26 PM, will have to made again. An urgent security update was made on the database today morning, and some changes made to algos may have be rolled back for some users

📣 NEW FUNCTIONALITY 📣 SL order placement delay for MTM SL Use case: Avoid MTM SL exits on price spikes. Documentation: https://quantiply.tech/documentation/advanced-settings/sl-order-placement-delay/#II._SL_order_placement_delay_f

⚠️ ❗️ANGELONE users ❗️⚠️ AngelOne users need to do the broker login (generate access token) using MPIN only. Password will not work, only MPIN will work tomorrow onwards. If you haven’t created an MPIN for your AngelOne account yet, then it can be done on https://trade.angelone.in/

⚠️ ❗️ZERODHA users ❗️⚠️ For some Zerodha users orders are not getting placed and are getting the error error:TokenException:Incorrect `api_key` or `access_token` Solution: 1. Re-do broker login from the Broker Login page (ie. re-generate access token) 2. Once broker login is re done, share the algo page links with @abhishah33 to reset the algos 3. Once algos are reset, you can disable the algos, wait for 5 secs and enable the algo again, and it will take positions without errors

📣 NEW SETTING for TARGET based RE-ENTRY / RE-EXECUTE This setting allows for a common count for re-entry/re-execute between Target and Stoploss re-entries or a separate individual count for Target based re-entry/re-execute and a separate count for Stoploss based re-entry/re-execute. There are 2 options to specify the max number of times that you want the re-entry/re-execute to happen for Target hit and/or Stoploss hit: 1. Individual 2. Common (As per Stockmock.in logic) Read detailed documentation here: https://quantiply.tech/documentation/advanced-settings/re-entry-max-count-type/

📣 NEW FEATURE 📣 TARGET based RE-ENTRY / RE-EXECUTE You can now re-enter positions that have hit the Target using, 1. Re-Cost( re-enter when the price comes back to entry price). 2. Re-Execute (re-enter immediately after the Target hits). 3. MTM Target based re-entry. Note: 1. Target based re-entry/re-execute functionality works exactly like the Stoploss based re-entry/re-execute. 2. Target based Re-Entry/Re-Execute and Stoploss based Re-Entry/Re-Execute can both be used together for each individual legs and also for MTM Target, all in the same algo.

⚠️ ❗️ANGEL ONE users ❗️⚠️ AngelOne users will not be able to trade today, as the algos will keep showing WAITING status due to the MasterContracts issue

⚠️ ❗️ANGEL ONE users ❗️⚠️ Orders are going into 'WAITING' status, and orders are not being placed. The issue with AngelOne is still there. Once resolved we will update

⚠️ ❗️ANGEL ONE users ❗️⚠️ AngelOne Master Contracts are fetched, you can now start trading. Users who have terminated algos can DM @abhishah33 the algo page links to get the algos reset

⚠️ ❗️ANGEL ONE users ❗️⚠️ AngelOne users can disable all algos for now. Once the issue is resolved, we will inform and you can enable the algos again

⚠️ ❗️ANGEL ONE users ❗️⚠️ Angel’s master contracts endpoint of the API is failing since morning. As of now, contracts aren’t being fetched. AngelOne users will not be able to trade today till the issue is resolved