⚠️ ❗️IIFL USERS ❗️⚠️
Quite a few IIFL users are getting this error for order placement, we have already raised this issue with IIFL. We will revert once this is resolved.
Error:
Gateway:Supplied Client [client id] Status Is [Deactivated].
Quite a few IIFL users are getting this error for order placement, we have already raised this issue with IIFL. We will revert once this is resolved.
Error:
Gateway:Supplied Client [client id] Status Is [Deactivated].
⚠️ ❗️IIFL USERS ❗️⚠️
Those getting the error Gateway:Supplied Client [client id] Status Is [Deactivated]. need to speak to their IIFL RM and get XTS re-activated.
Once XTS is re-activated you can send us the algo page link for the algos to be reset. Only the algos with this error will be reset
Those getting the error Gateway:Supplied Client [client id] Status Is [Deactivated]. need to speak to their IIFL RM and get XTS re-activated.
Once XTS is re-activated you can send us the algo page link for the algos to be reset. Only the algos with this error will be reset
📣 NEW BROKER LAUNCH 📣
Jainam Broking Limited (Jainam Duck)
Setup documentation: https://quantiply.tech/documentation/broker-setup/jainam-duck/
WARNING: Before doing broker login, make sure to logout of any Jainam product or Spark terminal.
Jainam Broking Limited (Jainam Duck)
Setup documentation: https://quantiply.tech/documentation/broker-setup/jainam-duck/
WARNING: Before doing broker login, make sure to logout of any Jainam product or Spark terminal.
⚠️ ❗️JAINAM DUCK USERS ❗️⚠️
Two important points to keep in mind:
1. Before doing broker login, make sure to logout of the Spark trading terminal and any other Jainam products/platforms that you might be logged in to from before. You can login to the terminal after broker login is done.
2. Do NOT enable TOTP, as TOTP is not working with broker login (for access token generation). You can use the PIN instead.
Two important points to keep in mind:
1. Before doing broker login, make sure to logout of the Spark trading terminal and any other Jainam products/platforms that you might be logged in to from before. You can login to the terminal after broker login is done.
2. Do NOT enable TOTP, as TOTP is not working with broker login (for access token generation). You can use the PIN instead.
⚠️ ❗️ALL USERS ❗️⚠️
A few users may be getting logged out of Quantiply on the mobile browsers. You can login to your desktops/laptops and it should work fine. This is a local storage issue in the browser, which will be resolved asap.
UPDATE: This issue was faced by less 20 users.
A few users may be getting logged out of Quantiply on the mobile browsers. You can login to your desktops/laptops and it should work fine. This is a local storage issue in the browser, which will be resolved asap.
UPDATE: This issue was faced by less 20 users.
📣 BROKER UPDATE 📣
Upstox API Version 2 is live on Quantiply. This is the new, improved & free version of the API which is open to all Upstox clients. Version 1 has been dropped from Quantiply.
New and existing Upstox API users have to create a new API app and do/re-do the setup as per Instructions shared here: https://quantiply.tech/documentation/broker-setup/upstox/
Upstox API Version 2 is live on Quantiply. This is the new, improved & free version of the API which is open to all Upstox clients. Version 1 has been dropped from Quantiply.
New and existing Upstox API users have to create a new API app and do/re-do the setup as per Instructions shared here: https://quantiply.tech/documentation/broker-setup/upstox/
⚠️ ❗️TRADEJINI USERS ❗️⚠️
There is an issue with the master contracts of Options. For Tradejini users trades will not get executed till the issue is resolved. Tradejini has been informed, and once the issue is resolved we will share an update.
There is an issue with the master contracts of Options. For Tradejini users trades will not get executed till the issue is resolved. Tradejini has been informed, and once the issue is resolved we will share an update.
⚠️ ❗️FINVASIA USERS ❗️⚠️
Error YEL:Yel not ready for transaction coming for order placement. Please check your algos.
You will have to place the order or square off manually, or get the algo reset
Error YEL:Yel not ready for transaction coming for order placement. Please check your algos.
You will have to place the order or square off manually, or get the algo reset
⚠️ ❗️FINVASIA USERS ❗️⚠️
16795 Order cancelled due to voluntary close out
Place SL orders manually immediately
16795 Order cancelled due to voluntary close out
Place SL orders manually immediately
⚠️ ❗️FINVASIA USERS ❗️⚠️
16795 Order cancelled due to voluntary close out
For users getting this error, Modify Settings of the algo, remove the SL setting, make it none, click SAVE, and then again Modify settings and add your SL setting and click SAVE. The algo will place the SL order again
16795 Order cancelled due to voluntary close out
For users getting this error, Modify Settings of the algo, remove the SL setting, make it none, click SAVE, and then again Modify settings and add your SL setting and click SAVE. The algo will place the SL order again
⚠️ ❗️FINVASIA USERS ❗️⚠️
Updated from Finvasia: Issue resolved!
Updated from Finvasia: Issue resolved!
⚠️ ❗️IIFL USERS ❗️⚠️
IIFL users would be getting this error for new orders being placed right now:
16643 : Options sell used limit exceeded the user limit.
IIFL users would be getting this error for new orders being placed right now:
16643 : Options sell used limit exceeded the user limit.
📣 NEW BROKER LAUNCH 📣
FLATTRADE
Brokerage: Zero brokerage
Setup documentation: https://quantiply.tech/documentation/broker-setup/flattrade/
Note:
Only 1 algo platform can be used at a time with Flattrade accounts
FLATTRADE
Brokerage: Zero brokerage
Setup documentation: https://quantiply.tech/documentation/broker-setup/flattrade/
Note:
Only 1 algo platform can be used at a time with Flattrade accounts
⚠️ ❗️FINVASIA USERS ❗️⚠️
Error YEL:Yel not ready for transaction
Please check your algos.
Error YEL:Yel not ready for transaction
Please check your algos.
⚠️ ❗️JAINAM DUCK USERS ❗️⚠️
Again pending SL orders have been cancelled. Please place SL orders manually
Again pending SL orders have been cancelled. Please place SL orders manually
⚠️ ❗️ANGEL ONE USERS ❗️⚠️
We're seeing a lot of errors for order placement and modifications, retries are also failing.
Error:
AB2001: Internal Error
We're seeing a lot of errors for order placement and modifications, retries are also failing.
Error:
AB2001: Internal Error
⚠️ ❗️ANGEL ONE USERS ❗️⚠️
Last error seen at 12:37:56, post that no errors. No full confirmation on whether the error will come again or not.
Error:
AB2001: Internal Error
Last error seen at 12:37:56, post that no errors. No full confirmation on whether the error will come again or not.
Error:
AB2001: Internal Error
⚠️ ❗️ANGEL ONE USERS ❗️⚠️
with reference to the Error:
AB2001: Internal Error
Scenario 1: If the error in your account has come for placement of entry/exit/stoploss orders you will see the error on the algo page under the leg
Scenario 2: If the error has come for fetching of order updates of your already placed orders, then you will not see the error but you will see the status of the leg 'WAITING'. These orders are placed and have to be managed manually, as algos are not getting order updates, instead getting the error in place of the order update from the broker.
Scenario 3: Both scenarios 1 and 2 occurring together.
with reference to the Error:
AB2001: Internal Error
Scenario 1: If the error in your account has come for placement of entry/exit/stoploss orders you will see the error on the algo page under the leg
Scenario 2: If the error has come for fetching of order updates of your already placed orders, then you will not see the error but you will see the status of the leg 'WAITING'. These orders are placed and have to be managed manually, as algos are not getting order updates, instead getting the error in place of the order update from the broker.
Scenario 3: Both scenarios 1 and 2 occurring together.
⚠️ ❗️UPSTOX USERS ❗️⚠️
This error would be coming for order placement: error:UDA PI100013:Origin header missing for this request
We have raised the issue with Upstox. We will revert once it is resolved by the broker.
This error would be coming for order placement: error:UDA PI100013:Origin header missing for this request
We have raised the issue with Upstox. We will revert once it is resolved by the broker.
⚠️ ❗️UPSTOX USERS ❗️⚠️
ISSUE RESOLVED! As updated by Upstox.
With reference to error: error:UDA PI100013:Origin header missing for this request
ISSUE RESOLVED! As updated by Upstox.
With reference to error: error:UDA PI100013:Origin header missing for this request