📣 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
⚠️ ❗️JAINAM DUCK USERS ❗️⚠️
Master contracts end point is having an issue, contracts are not being fetched from the broker. Jainam users will not be able to trade till the issue is resolved from the brokers side and the contracts are fetched. We have informed Jainam.
Master contracts end point is having an issue, contracts are not being fetched from the broker. Jainam users will not be able to trade till the issue is resolved from the brokers side and the contracts are fetched. We have informed Jainam.
⚠️ ❗️JAINAM DUCK USERS ❗️⚠️
Contracts fetched, issue resolved. To run algos make sure to DISABLE and ENABLE the algos as algos need to be RESTARTED. Already running algos will not work, they have to be restarted.
Contracts fetched, issue resolved. To run algos make sure to DISABLE and ENABLE the algos as algos need to be RESTARTED. Already running algos will not work, they have to be restarted.
⚠️ ❗️UPSTOX USERS ❗️⚠️
Average price is not coming from the broker. There is an issue with this data point coming from the broker.
Square off and terminate the algos running on Upstox. We have raised the issue with the broker. Once resolved, we will announce and you can resume your trading on Upstox
Average price is not coming from the broker. There is an issue with this data point coming from the broker.
Square off and terminate the algos running on Upstox. We have raised the issue with the broker. Once resolved, we will announce and you can resume your trading on Upstox
⚠️ ❗️ALL USERS ❗️⚠️
Trading holiday on account of Bakri ID has been revised to 29th June 2023 from 28th June 2023. Tomorrow will NOT be a trading holiday. Thursday is a trading holiday.
Trading holiday on account of Bakri ID has been revised to 29th June 2023 from 28th June 2023. Tomorrow will NOT be a trading holiday. Thursday is a trading holiday.
⚠️ ❗️UPSTOX USERS ❗️⚠️
The average price issue is not yet resolved. Upstox users, do not run algos till we confirm with the broker that the issue is resolved
The average price issue is not yet resolved. Upstox users, do not run algos till we confirm with the broker that the issue is resolved