Quantiply.tech

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

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

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.

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

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.

📣 FEATURE UPDATES 📣 2 new features: 1. Clientwise Stoploss & Target (Global Stoploss & Target). 2. Square off individual legs with multi-select option.

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

📣 QUANTIPLY now supports FINVASIA 🔥 Quick setup tutorial: youtu.be/W2zkzmSKBKQ

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

⚠️ Zerodha API now running. Quantiply + Zerodha should work fine. But do monitor as this widespread network issue may not have been fully restored. Zerodha & Upstox can both be accessed using your Jio mobile or wifi services ⚠️

⚠️Change your internet connectivity to JIO and you should be able to access Zerodha and Upstox both. Positions can be manually managed through the terminal ⚠️

⚠️ Upstox errors: Lot of Time Out errors from Upstox⚠️ Enter, square off or manage Zerodha positions manually for legs which are giving this error Seems like a possible network outage with Upstox and Zerodha

⚠️ Zerodha errors: Lot of NetworkException:No response from server with error code: ECONNABORTED errors from Zerodha⚠️ Enter, square off or manage Zerodha positions manually for legs which are giving this error

⚠️ For all IIFL users ⚠️ Today's IIFL issue is resolved. Trading can be done tomorrow

⚠️ For all IIFL users ⚠️ Terminate all algos that are Trade Active after squaring off positions from TTWEB. Use the Terminate button and NOT the Square off all positions and terminate algo button. This will simply terminate the algo and not fire any square off orders for positions that might have gotten executed in the morning while IIFL's API issue was going on.

⚠️ Latest message from IIFL: ⚠️ MIS positions in ttblaze/xts will not be squared off today at 3:20. Please square off manually from your terminals

⚠️ Latest message from IIFL: ⚠️ 1. Please check your positions on IIFL TTWEB application. All positions showing on IIFL TTWEB application are correct and can be squared off from there. Actual positions are correctly synced on TTWEB 2. Do not place any orders via Blaze API till issue resolved. Issue is not yet resolved with Blaze/Blaze API 3. Cancel all open orders placed earlier from Blaze web terminal

⚠️ Message from IIFL: ⚠️ Please check your positions on IIFL TT WEB OR MARKET APP AND manage your positions from there. We are working on API issue

⚠️ IIFL facing issues with order placements and order updates. Issue will be resolved in 5-10 mins as per IIFL ⚠️

⚠️ Upstox has resolved the broker login/token generation issue, you can now broker login, disable and enable your algos to start trading⚠️