⚠️ ❗️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
⚠️ ❗️ALL USERS ❗️⚠️
There is an issue with the MTM SL counter where the MTM SL is showing 0. This issue would be coming for a specific setting and not for all algos.
Please check your MTM SL counters.
Solution: Click on MODIFY SETTINGS button and then just click SAVE SETTINGS, and the counter will be reset
This issue will be resolved today itself
There is an issue with the MTM SL counter where the MTM SL is showing 0. This issue would be coming for a specific setting and not for all algos.
Please check your MTM SL counters.
Solution: Click on MODIFY SETTINGS button and then just click SAVE SETTINGS, and the counter will be reset
This issue will be resolved today itself
⚠️ ❗️ZERODHA USERS ❗️⚠️
Zerodha users would be getting the error: The exchange connection (adapter) did not accept the order. Please retry.
for order placement
Next steps:
If this error is coming for Entry orders, then you can place the entry orders manually or get the algo reset
If this error is coming for advance SL orders, then you can modify settings and change the SL setting value, click save, and then again modify settings and put the original SL setting and click Save, this will make the algo place the SL order again
If this error has come for Exit orders, then you will have to manually exit the order
Zerodha users would be getting the error: The exchange connection (adapter) did not accept the order. Please retry.
for order placement
Next steps:
If this error is coming for Entry orders, then you can place the entry orders manually or get the algo reset
If this error is coming for advance SL orders, then you can modify settings and change the SL setting value, click save, and then again modify settings and put the original SL setting and click Save, this will make the algo place the SL order again
If this error has come for Exit orders, then you will have to manually exit the order
⚠️ ❗️IIFL USERS ❗️⚠️
IIFL API is timing out. Orders may or may not be getting placed. Check terminals after the algo fires the orders. Even if the orders are executed order updates from the brokers may not be coming and the legs will show 'WAITING' status. And the trades would have to be managed manually
IIFL API is timing out. Orders may or may not be getting placed. Check terminals after the algo fires the orders. Even if the orders are executed order updates from the brokers may not be coming and the legs will show 'WAITING' status. And the trades would have to be managed manually