⚠️ ❗️FINVASIA USERS ❗️⚠️
UPDATE from FINVASIA
🚫 API is still working slow. Orders may get placed at the exchange when orders are fired, but will not reflect on your algo dashboards immediately.
✅ Web terminal issue resolved, and working fine. Positions can be viewed and managed.
It is advised to AVOID TRADING right now to avoid mismanagement and confusion
UPDATE from FINVASIA
🚫 API is still working slow. Orders may get placed at the exchange when orders are fired, but will not reflect on your algo dashboards immediately.
✅ Web terminal issue resolved, and working fine. Positions can be viewed and managed.
It is advised to AVOID TRADING right now to avoid mismanagement and confusion
⚠️ ❗️FINVASIA USERS ❗️⚠️
UPDATE from FINVASIA
✅ API issues fixed.
But please be careful and monitor if you are going to take trades
UPDATE from FINVASIA
✅ API issues fixed.
But please be careful and monitor if you are going to take trades
⚠️ ❗️ANGELONE USERS ❗️⚠️
Error coming for order placement: -:429:Too Many Requests;-
Use the retry individual leg functionality.
This is some new error, we've forwarded the issue to Angel
Error coming for order placement: -:429:Too Many Requests;-
Use the retry individual leg functionality.
This is some new error, we've forwarded the issue to Angel
⚠️ ❗️ANGELONE USERS ❗️⚠️
Error coming for order placement: -:429:Too Many Requests;-
Retry option may work or may give the error again. Even if the retry is successful, it is possible that you will get the error when your MTM SL is hit, so it is very risky. Monitor your positions as you will also have to manage MTM SL or Target / end time exits manually
Till the time Angel doesn't give a confirmation that the issue is resolved, don't take new trades.
Error coming for order placement: -:429:Too Many Requests;-
Retry option may work or may give the error again. Even if the retry is successful, it is possible that you will get the error when your MTM SL is hit, so it is very risky. Monitor your positions as you will also have to manage MTM SL or Target / end time exits manually
Till the time Angel doesn't give a confirmation that the issue is resolved, don't take new trades.
⚠️ ❗️ANGELONE USERS ❗️⚠️
DO NOT TAKE POSITIONS TILL THE ISSUE IS RESOLVED BY ANGEL COMPLETELY
We will announce once the issue is resolved.
DO NOT TAKE POSITIONS TILL THE ISSUE IS RESOLVED BY ANGEL COMPLETELY
We will announce once the issue is resolved.
⚠️ ❗️ANGELONE USERS ❗️⚠️
✅ Issue is resolved by Angel
Use the retry individual leg option to retry legs in error
✅ Issue is resolved by Angel
Use the retry individual leg option to retry legs in error
⚠️ ❗️AC AGARWAL USERS ❗️⚠️
Broker login is failing, ACA is checking the issue and resolving asap. We will update once the issue is resolved.
Broker login is failing, ACA is checking the issue and resolving asap. We will update once the issue is resolved.
⚠️ ❗️AC AGARWAL USERS ❗️⚠️
ACA issue resolved, you can broker login now.
Disable the Algos, wait for 5 secs and enable the algo, and they will go into ready status and start running
ACA issue resolved, you can broker login now.
Disable the Algos, wait for 5 secs and enable the algo, and they will go into ready status and start running
⚠️ ❗️KOTAK NEO USERS ❗️⚠️
You may see this circuit limit error while squaring off some of your open positions
RMS:Rule: Check circuit limit including square off order exceeds for entity account-XXXXX across exchange across segment across product
If you see this error, you can modify your limit/SL Limit order buffer settings to percentage from points, save settings and then use the retry option. It will place the SL order again.
Since this is a new error observed today for the first time, it will now be added to the algos error handling process.
You may see this circuit limit error while squaring off some of your open positions
RMS:Rule: Check circuit limit including square off order exceeds for entity account-XXXXX across exchange across segment across product
If you see this error, you can modify your limit/SL Limit order buffer settings to percentage from points, save settings and then use the retry option. It will place the SL order again.
Since this is a new error observed today for the first time, it will now be added to the algos error handling process.
⚠️ ❗️ALL USERS ❗️⚠️
Live feed not running
We're checking the issue and fixing it. Till then new positions will not get executed. And open positions that don't have SL orders placed in advance will have to be manually managed
Live feed not running
We're checking the issue and fixing it. Till then new positions will not get executed. And open positions that don't have SL orders placed in advance will have to be manually managed
⚠️ ❗️AC AGARWAL USERS ❗️⚠️
Voluntary close out error
Pending SL orders would be cancelled
use the Retry individual leg option to place SL orders again
Voluntary close out error
Pending SL orders would be cancelled
use the Retry individual leg option to place SL orders again
⚠️ ❗️ALL USERS ❗️⚠️
There is a network issue at the data center. Some of our systems are not accessible currently, some are working on backups. The service provider is resolving the issue at the earliest.
There is a network issue at the data center. Some of our systems are not accessible currently, some are working on backups. The service provider is resolving the issue at the earliest.
⚠️ ❗️ALL USERS ❗️⚠️
For POSITONAL ALGOS, all positions will have to be managed manually or squared off. Once the systems starts running the POSITIONAL ALGOS will also get activated automatically and it will follow conditions and enter and exit. There is no way to TERMINATE the POSITIONAL algos from our side right now.
INTRADAY ALGOS: Once the systems are operational, you will have to disable and enable the algos to make it run
For POSITONAL ALGOS, all positions will have to be managed manually or squared off. Once the systems starts running the POSITIONAL ALGOS will also get activated automatically and it will follow conditions and enter and exit. There is no way to TERMINATE the POSITIONAL algos from our side right now.
INTRADAY ALGOS: Once the systems are operational, you will have to disable and enable the algos to make it run
⚠️ ❗️ALL USERS ❗️⚠️
Website will load, but please DO NOT enable algos till all systems are running. We will announce once everything is operational within the next 30 mins
Website will load, but please DO NOT enable algos till all systems are running. We will announce once everything is operational within the next 30 mins
⚠️ ❗️ALL USERS ❗️⚠️
While the servers are running and network is restored, we're still waiting for the Service Provider to complete sanity checks before we make the system operational, the time given to us was 30 mins, but the process is still ongoing.
We will update as soon as the system is fully operational.
While the servers are running and network is restored, we're still waiting for the Service Provider to complete sanity checks before we make the system operational, the time given to us was 30 mins, but the process is still ongoing.
We will update as soon as the system is fully operational.
⚠️ ❗️ALL USERS ❗️⚠️
RCA (Root Cause Analysis) of the downtime:
Today we’ve had the worst ever downtime seen in the past 3 years of being operational.
Root cause:
A domino of network switches failure, internal network failure and failure to re route network traffic via backups at the primary data centre of the Service Provider and finally storage being inaccessible due to fail safes that come on by default in the latest generation server architecture that we’re using.
Since the issue has been going on since before 8 AM today, our primary systems had not started and inturn not started backup systems as well. Issue was faced by all primary systems at the same time.
Plan Of Action to avoid a scenario like this:
1. In the near term/medium term, have the backup system deployed and running with a completely different service provider in a different geography.
2. Have more than 2 instances that can act as master systems to trigger different systems. While a version of this was already operational, it was a complete failure at different levels for an extended period of time which din’t allow us to attempt an early morning restoration.
3. Work with multiple generations of server architecture.
Compensation to our users:
1. Intraday Algos: We will be crediting users with 2x credits for today based on the number of Algos subscribed for today.
2. Positional algos: 2x credits will be credited for all positional algos for each day it was running till today.
These credits will automatically be added to your Quantiply accounts tomorrow or day after.
It is an extremely frustrating incident for all users, which were are extremely apologetic about. We want to thank you for your patience, understanding and positive reinforcement. We have identified ways to avoid disruption of services specific to this issue.
Note: Issue is resolved but we're implementing certain things as per the recommendation of the Cloud Service Provider. It will take time till tomorrow morning for the system to be fully operational and come online.
RCA (Root Cause Analysis) of the downtime:
Today we’ve had the worst ever downtime seen in the past 3 years of being operational.
Root cause:
A domino of network switches failure, internal network failure and failure to re route network traffic via backups at the primary data centre of the Service Provider and finally storage being inaccessible due to fail safes that come on by default in the latest generation server architecture that we’re using.
Since the issue has been going on since before 8 AM today, our primary systems had not started and inturn not started backup systems as well. Issue was faced by all primary systems at the same time.
Plan Of Action to avoid a scenario like this:
1. In the near term/medium term, have the backup system deployed and running with a completely different service provider in a different geography.
2. Have more than 2 instances that can act as master systems to trigger different systems. While a version of this was already operational, it was a complete failure at different levels for an extended period of time which din’t allow us to attempt an early morning restoration.
3. Work with multiple generations of server architecture.
Compensation to our users:
1. Intraday Algos: We will be crediting users with 2x credits for today based on the number of Algos subscribed for today.
2. Positional algos: 2x credits will be credited for all positional algos for each day it was running till today.
These credits will automatically be added to your Quantiply accounts tomorrow or day after.
It is an extremely frustrating incident for all users, which were are extremely apologetic about. We want to thank you for your patience, understanding and positive reinforcement. We have identified ways to avoid disruption of services specific to this issue.
Note: Issue is resolved but we're implementing certain things as per the recommendation of the Cloud Service Provider. It will take time till tomorrow morning for the system to be fully operational and come online.
⚠️ ❗️ALL USERS ❗️⚠️
The Subscription module will be unavailable till evening till the compensation credits are added to all the users accounts. This means that you will not be able to upgrade/downgrade plans or increase/decrease algo count temporarily till evening. Once the subscriptions module is activated again, we will announce.
The Subscription module will be unavailable till evening till the compensation credits are added to all the users accounts. This means that you will not be able to upgrade/downgrade plans or increase/decrease algo count temporarily till evening. Once the subscriptions module is activated again, we will announce.
⚠️ ❗️ALL USERS ❗️⚠️
Credits are added. Subscriptions module is active
Credits are added. Subscriptions module is active
⚠️ ❗️ALL USERS ❗️⚠️
Positional algos running from before Friday or Friday will not be launched tomorrow. Those have been terminated to avoid it from running without you knowing it’s running. Fresh Positional algos can be run, but the older ones will not run.
Positional algos running from before Friday or Friday will not be launched tomorrow. Those have been terminated to avoid it from running without you knowing it’s running. Fresh Positional algos can be run, but the older ones will not run.