Quantiply.tech
5.98K subscribers
110 photos
17 videos
3 files
108 links
Download Telegram
⚠️ ❗️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 ❗️⚠️

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

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
⚠️ ❗️ALL users ❗️⚠️

Some updates are being pushed. The website will be unavailable for sometime
This media is not supported in your browser
VIEW IN TELEGRAM
📣 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
⚠️ ❗️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 have 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.
📣 RE-PLACEMENT OF EXIT ORDERS in case of:
(1) CIRCUIT LIMIT ERRORS
(2) MULTIPLE OTHER BROKER SPECIFIC ERRORS
📣

In the case of circuilt limit errors coming for placement of SL orders which are being placed in advance, and, multiple other broker specific errors coming for SL order placement due to which SL orders did not get placed, the algo will continously monitor the price and place the exit order (SL order) at the time the SL is hit

The exit will happen normally in case any other type of exit like Target hit, MTM SL/Target or end time is triggered

The error message will continue to show on the algo page under the leg that got the error, even while algo is continously mornitoring the price of that leg. The error message will disappear only when a square off happens later in the day.

The re-placed SL orders will be placed as per the exit order type selected ie. Limit/SL Limit OR Market orders.
⚠️ ❗️ANGELONE USERS ❗️⚠️

Angel users are getting AB2001: Internal Error for order placement
We have updated Angel about it
QUANTIPLY users can now trade current week, weekly Options contracts & current month Futures contract of FINNIFTY

NOTE:

1. FINNIFTY weekly contracts expire on Tuesday every week.

2. For ZERODHA users,
- MIS orders are blocked in less liquid FINNIFTY strikes.
- NRML order type will work for all strikes.
- MARKET orders are only allowed for ATM option contracts, i.e. up to 1% ITM/OTM.
- LIMIT/SL-LIMIT orders allowed for all strikes.

3. For UPSTOX users,
- Only NRML allowed in all strikes. MIS orders are not allowed.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.

4. For IIFL users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.

5. For FINVASIA users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.

6. For ANGELONE users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.

7. The functionality of order conversion from Limit/SL-Limit to Limit//SL-Limit after N secs, which would be useful only for ZERODHA will be added in the coming days. It is advised to keep Limit/SL-Limit buffers on the higher side if you are trading with ZERODHA, so as to make sure the order is executed and conversion can be avoided till the functionality is added.
⚠️ ❗️ANGELONE USERS ❗️⚠️

Angel users are getting AB2001: Internal Error for order placement
We have updated Angel about it.

Check if legs that are giving this error are executed or not. If executed, place SL orders manually
⚠️ ❗️ALL USERS ❗️⚠️

For Wait & Trade entries, this week, use MARKET orders to enter. Limit orders placed in advance are giving circuit limit rejections and hence are not getting placed in some cases.
⚠️ ❗️ALL USERS ❗️⚠️

For Wait & Trade entries, for tomorrow, use MARKET orders to enter. Limit orders placed in advance may give circuit limit rejections and trades will not be taken
⚠️ ❗️ALL USERS ❗️⚠️

The 'Exit selected legs' functionality will not work today due to a UI issue. It will be fixed after market today.

All other functionalities will work normally.
⚠️ ❗️ANGELONE USERS ❗️⚠️

Some AngelOne users would be geting 502:Bad Gateway errors.

Check if legs that are giving this error are executed or not. If executed, place SL orders manually

You can get your algos reset from @abhishah33
⚠️ ❗️ANGELONE USERS ❗️⚠️

AngelOne master contracts API is not returning any contracts data. If this issue continues beyond 9:00 AM today, AngelOne users will NOT be able to trade for the day.
⚠️ ❗️ANGELONE USERS ❗️⚠️

Master Contracts have been fetched. AngelOne users will be able to trade today
⚠️ ❗️ALL USERS ❗️⚠️

There seems to be an issue with client wise Target and SL calculation (portfolio level SL & target). If you have set any client wise Target or SL, please set it to '0' value temporarily. We're checking and addressing the issue right away
⚠️ ❗️IIF USERS ❗️⚠️

There is a '400' error that is coming for order placement for IIFL clients. IIFL has been informed. Once it is resolved, we will update. This is an error from IIFL's side, not Quantiply
⚠️ ❗️IIF USERS ❗️⚠️

IIFL has resolved the '400' error issue
⚠️ ❗️ALL USERS ❗️⚠️

Client wise Target and SL (portfolio level SL & target) issue that affected a handful of users has been resolved. You can now configure the Client wise SL or Target for your client ids