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.
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
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.
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
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
⚠️ ❗️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
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 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 ✅
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
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
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
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
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
⚠️ ❗️FINVASIA USERS ❗️⚠️
Finvasia API response is slow and is timing out. So some orders placed may show 'WAITING' status, as algo is waiting for the broker's api to provide order status. Please keep a watch, and check if orders are placed but showing waiting status. Only once the order status comes, can the algo place SL orders. Till then the SL orders have to be placed manually.
Finvasia API response is slow and is timing out. So some orders placed may show 'WAITING' status, as algo is waiting for the broker's api to provide order status. Please keep a watch, and check if orders are placed but showing waiting status. Only once the order status comes, can the algo place SL orders. Till then the SL orders have to be placed manually.
⚠️ ❗️FINVASIA USERS ❗️⚠️
Some Finvasia users are getting Invalid App key and Invalid Vendor Code error while doing broker login for Finvasia. We have raised the issue with Finvasia. We will revert as soon as they have resolved the issue
Some Finvasia users are getting Invalid App key and Invalid Vendor Code error while doing broker login for Finvasia. We have raised the issue with Finvasia. We will revert as soon as they have resolved the issue
⚠️ ❗️FINVASIA USERS ❗️⚠️
Broker login issue is resolved
Broker login issue is resolved
⚠️ ❗️FINVASIA USERS ❗️⚠️
!IMPORTANT!
All Finvasia users are requested to regenerate access token, ie. Re-do broker login from the broker login page immediately as Finvasia has restarted their system due to an urgent upgrade on their system
!IMPORTANT!
All Finvasia users are requested to regenerate access token, ie. Re-do broker login from the broker login page immediately as Finvasia has restarted their system due to an urgent upgrade on their system
⚠️ ❗️FINVASIA USERS ❗️⚠️
For the following errors that come during broker login
1. Invalid app key
2. Invalid vendor code
You will have to re-generate the api key from the PRISM portal and put the new api key in the broker setup page.
The new api key will be active only after 2 hours of being generated, so broker login can be done only after 2 hours and algos will function thereafter
For the following errors that come during broker login
1. Invalid app key
2. Invalid vendor code
You will have to re-generate the api key from the PRISM portal and put the new api key in the broker setup page.
The new api key will be active only after 2 hours of being generated, so broker login can be done only after 2 hours and algos will function thereafter
⚠️ ❗️FINVASIA USERS ❗️⚠️
Finvasia users getting the error Yel not ready for transaction for order placement. We have raised the issue with Finvasia
You can DM algo page links, get the algos reset and try again. We will also update once the issue is resolved
Finvasia users getting the error Yel not ready for transaction for order placement. We have raised the issue with Finvasia
You can DM algo page links, get the algos reset and try again. We will also update once the issue is resolved
⚠️ ❗️FINVASIA USERS ❗️⚠️
Do not re-try placing orders after the algo has been reset. Once the broker confirms the issue is resolved, we will confirm, post which you can re-try again. Do not place orders till issue is resolved
Do not re-try placing orders after the algo has been reset. Once the broker confirms the issue is resolved, we will confirm, post which you can re-try again. Do not place orders till issue is resolved
⚠️ ❗️FINVASIA USERS ❗️⚠️
Orders are now going through. You can run the algos again
Orders are now going through. You can run the algos again
⚠️ ❗️FINVASIA USERS ❗️⚠️
for those getting the error 16795: Order cancelled due to voluntary close out should place SL orders manually or just square off all positions of that algo, get the algo reset and run the algo again
What is voluntary close out?
https://www.nseindia.com/products-services/equity-market-voluntary-close-out
for those getting the error 16795: Order cancelled due to voluntary close out should place SL orders manually or just square off all positions of that algo, get the algo reset and run the algo again
What is voluntary close out?
https://www.nseindia.com/products-services/equity-market-voluntary-close-out