⚠️ ❗️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.
⚠️ ❗️FINVASIA USERS ❗️⚠️
Broker login not happening. And login to Shoonya terminal not happening. We have raised the issue with Finvasia.
Broker login not happening. And login to Shoonya terminal not happening. We have raised the issue with Finvasia.
⚠️ ❗️FINVASIA USERS ❗️⚠️
Broker login and login to Shoonya terminal is working now. There is no official update from Finvasia yet, but it seems to be working.
Broker login and login to Shoonya terminal is working now. There is no official update from Finvasia yet, but it seems to be working.
📣 NEW FEATURE 📣
1. AUTO SQUARE OFF OPEN LEGS ON MARGIN ERRORS: https://quantiply.tech/documentation/other-features/auto-exit-on-margin-error/
2. RETRY BUTTONS FOR INDIVIDUAL LEGS ON ERRORS: https://quantiply.tech/documentation/other-features/retry-button-for-individual-orders/
1. AUTO SQUARE OFF OPEN LEGS ON MARGIN ERRORS: https://quantiply.tech/documentation/other-features/auto-exit-on-margin-error/
2. RETRY BUTTONS FOR INDIVIDUAL LEGS ON ERRORS: https://quantiply.tech/documentation/other-features/retry-button-for-individual-orders/
⚠️ ❗️FINVASIA USERS ❗️⚠️
Broker login not working and throwing errors. We have raised the issue with finvasia, we will announce once the issue is resolved
Broker login not working and throwing errors. We have raised the issue with finvasia, we will announce once the issue is resolved
⚠️ ❗️ALL USERS ❗️⚠️
There is some issue with the system, orders are not getting placed, we're checking
There is some issue with the system, orders are not getting placed, we're checking
⚠️ ❗️ALL USERS ❗️⚠️
Issue resolved.
Instructions:
1. For all algos which are in READY status and have not yet fired orders, these algos will work properly, no need to disable and enable or reset algos
2. For all algos that have already run and are showing WAITING status, please share the algo page links for ALGO RESET with @quantiplysupport or on Whatsapp (+918369560753). Once the algos are reset disable the algos, and enable it and it will run properly
Issue resolved.
Instructions:
1. For all algos which are in READY status and have not yet fired orders, these algos will work properly, no need to disable and enable or reset algos
2. For all algos that have already run and are showing WAITING status, please share the algo page links for ALGO RESET with @quantiplysupport or on Whatsapp (+918369560753). Once the algos are reset disable the algos, and enable it and it will run properly
⚠️ ❗️FINVASIA USERS ❗️⚠️
Error YEL:Yel not ready for transaction
Please check your algos.
Error YEL:Yel not ready for transaction
Please check your algos.
⚠️ ❗️ALL USERS ❗️⚠️
We faced an issue in the morning with the propagation and replication of master contracts across multiple servers due to which all parts of the contracts data were not correctly loaded and the orders were in waiting status. Since only some parts of the data like lot size were missing it was impossible to preempt or identify this issue till it occured. This was caused due to network issues within the private networks.
We have implemented a workaround for this specific issue. We will also be implementing another backup solution for the same in the coming days to avoid this from happening again.
We faced an issue in the morning with the propagation and replication of master contracts across multiple servers due to which all parts of the contracts data were not correctly loaded and the orders were in waiting status. Since only some parts of the data like lot size were missing it was impossible to preempt or identify this issue till it occured. This was caused due to network issues within the private networks.
We have implemented a workaround for this specific issue. We will also be implementing another backup solution for the same in the coming days to avoid this from happening again.