⚠️ ❗️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
⚠️ ❗️AC AGARWAL USERS❗️⚠️
AC Agarwal's symphony XTS is down. Broker login is also failing. Issue is raised with the broker, should get resolved in a bit.
AC Agarwal's symphony XTS is down. Broker login is also failing. Issue is raised with the broker, should get resolved in a bit.
⚠️ ❗️AC AGARWAL USERS❗️⚠️
AC Agarwal Symphony XTS is up now. You will be able to broker login
AC Agarwal Symphony XTS is up now. You will be able to broker login
⚠️ ❗️UPSTOX USERS ❗️⚠️
Average price issue is RESOLVED by the broker. Upstox users can resume trading.
Average price issue is RESOLVED by the broker. Upstox users can resume trading.
⚠️ ❗️FINVASIA USERS ❗️⚠️
Orders are being fired by the algo but are not being processed by Finvasia and orders showing WAITING status. Issue is raised with Finvasia. We will update once resolved
Orders are being fired by the algo but are not being processed by Finvasia and orders showing WAITING status. Issue is raised with Finvasia. We will update once resolved
⚠️ ❗️FINVASIA USERS ❗️⚠️
It seems FINNIFTY orders are going through. Please disable NIFTY and BANKNIFTY algos till the issue is resolved. We're checking with the broker what exactly the issue is
It seems FINNIFTY orders are going through. Please disable NIFTY and BANKNIFTY algos till the issue is resolved. We're checking with the broker what exactly the issue is
⚠️ ❗️FINVASIA USERS ❗️⚠️
Finvasia Issue resolved! Master contracts missing from their master contracts list.
All algos that are not yet run will have to be restarted by DISABLING and ENABLING the algo. DISABLE the algo and wait for 5 secs, and then ENABLE the algo to restart.
Algos that have already run but were stuck in WAITING status can be reset by us and run by you again. Send algo page links to @quantiplysupport.
Finvasia Issue resolved! Master contracts missing from their master contracts list.
All algos that are not yet run will have to be restarted by DISABLING and ENABLING the algo. DISABLE the algo and wait for 5 secs, and then ENABLE the algo to restart.
Algos that have already run but were stuck in WAITING status can be reset by us and run by you again. Send algo page links to @quantiplysupport.