Quantiply.tech

⚠️ Algos have not gone into Ready status. We’re checking the issue. Will update once the issue is resolved⚠️

POSITIONAL TRADES RELEASE NOTES {Continued..}: VII. Special case error: In the case where one of the days in the week is a trading holiday, the end day or (N) days before expiry setting will have to be set appropriately, or the algo will throw a runtime error just when the orders are fired at the start time. For example: If Thursday is a trading holiday, and expiry is on Wednesday, then the setting for a position opened on Friday which is to be exited on Monday will have to be N = 2 days before expiry and not N = 3. In the case this error occurs, you will see a error warning icon on the homepage next to the algo, and an error message under the End day setting on the algo configuration page. Upon changing the setting (ie. reducing the days) the algo will immediately fire the entry orders.

NEW FEATURE LAUNCH POSITIONAL TRADES With Quantiply, you can now carry forward positions to (1) the next day, (2) till expiry or (3) specific number of days before expiry. RELEASE NOTES: I. Select Trade type - Positional to configure a positional or carry forward trade. II. There are 2 options to select the Duration of the trade: 1. STBT/BTST (Sell today buy tomorrow/Buy today sell tomorrow): This option will square off positions the very next day. ie. the positions taken today will be squared off the next day. 2. (N) days before expiry: This option will allow trades to be carry forwarded all the way till the expiry day or a specific number of days before the expiry day. For example: with setting N = 0 days before expiry, the algo will square off the positions on the day of the expiry. With setting N = 1, the algo will square off the positions 1 day before the expiry day, and so on. III. Setting Check condition next day after (time): The algo will check all SL, Target conditions and place orders only after the time given under this setting the next morning, for all days, for the entire duration of the trade. For example: if the time is set to 09:30:00 then the algo will check if any or all SL or Target conditions are met and square off orders only after 09:30:00 on the next trading day. This setting can be modified even when trade is active during market hours and off market hours. IV. Trailing frequency interval setting has been moved to under Advanced Settings. V. It is advisable to set Check condition next day after (time) to something later than 09:17:00 to avoid any early morning API errors from the broker, as the broker’s systems are going through heavy loads in the first couple of minutes at market open. VI. While the trade is active, if you modify the Duration setting from (N) days before expiry to STBT/BTST, and if the trade has already been active for more than 2 days and crossed the day 2, the algo will immediately square off positions upon changing from (N) days before expiry to STBT/BTST. For example: If a trade is taken on a friday with (N) days before expiry setting 0, and on Tuesday or Wednesday, one were to change the Duration setting from (N) days before expiry to STBT/BTST, the algo will immediately exit all positions as Monday which would be the STBT/BTST exit day, has been crossed.

⚠️ ISSUE RESOLVED: Zerodha API showing not running in the System monitor.

⚠️ Zerodha API showing not running in the System monitor. This is an error in the system monitor on Quantiply itself, the API is running fine & all orders will go through without an issue

⚠️ Some algos for some users have not gone into ’Ready’ status. They’re stuck in ‘Enabled’ status. Please check the status of your algos and ‘Disable’ and ‘Enable’ to put it in ‘Ready’ status

⚠️ IIFL ISSUE RESOLVED Orders can be fired now

⚠️ IIFL is throwing an error for all orders: 400 - {"type":"error","code":"e...... Issue will get resolved in 15 mins according to IIFL, once resolved we will update.

⚠️IIFL issue resolved

⚠️ IIFL is throwing an error for all orders: 400 - {"type":"error","code":"e-orders-0009","description":"Gateway:Order Manager Server Is Not Running."} IIFL has been informed. They’re checking. Will revert as soon as it is resolved

⚠️ Upstox broker login failing for all Upstox users. Error: “ {"message":"Missing Authentication Token"}” We have informed Upstox about it. Will update as soon as it is resolved

⚠️ AngelOne users, check for Quarterly settlement done in your accounts. Please check if they’ve transferred money to your bank account and transfer it back to avoid margin shortfall

⚠️ZERODHA API throwing "NetworkException:No response from server with error code: ECONNABORTED" errors⚠️ ENTRIES & EXITS are not happening as expected, so, will have to be done manually

⚠️ZERODHA API throwing "NetworkException:No response from server with error code: ECONNABORTED" errors⚠️ Monitor positions, exits are not happening as expected

⚠️ UPSTOX API ISSUE RESOLVED ✅ ⚠️ Order modifications and cancellations are now working fine

⚠️ UPSTOX API ISSUE ⚠️ Upstox's issue continues till date. Order modifications and order cancellations are failing. Unfortunately Upstox is just not able to resolve this issue quick enough permanently, which is a shame. Solution 1: Use only Market orders for entry and exit (as order placement is working fine). This is not a great solution as Market orders carry a risk of freak trades and higher slippages Solution 2: Shift to any other broker completely - IIFL, Zerodha or Angel

⚠️ UPSTOX API ISSUE ⚠️ Upstox facing issues with order updates, modifications and cancellations. Orders are getting placed but order updates are missing. Algo will not be able to place any SL orders or exit on MTM Target or MTM SL. Manage manually till Upstox resolves the issue

When a broker's API is down, and new orders are not getting executed.. - Previously placed SL Limit or Limit orders, will get executed normally, as these orders are already in the exchange's system. But since the API is down, your Quantiply dashboard will not be able to show order updates ie. average exit price & time of the executed order, at that time - Trailing of SLs will not work, SL limit/limit orders will not get modified with the new SL, once the API is back online, the already placed SL orders will get trailed to the latest SL directly. - Individual leg target and MTM based SL or Target orders which the algo fires at the time, will throw errors and have to be monitored and managed manually from the broker's terminal. Once the API is back online, the algo will immediately fire orders if the trade has crossed the MTM Target or MTM Stoploss. - If the trade has been managed manually or exited completely while the API was down, then you need to Terminate the algo as well. This is because when the API is back online, and any Target or SL conditions get fulfilled, the algo will try to exit orders. To avoid any unwanted orders being fired the algo should be Terminated if all the positions have been exited earlier