⚠️ AngelOne users: ⚠️
Login issue has been resolved.
No confirmation on whether the issues with 500 error and other errors are resolved. Wait for our announcement before firing algos again
Login issue has been resolved.
No confirmation on whether the issues with 500 error and other errors are resolved. Wait for our announcement before firing algos again
⚠️ AngelOne users: ⚠️
Angel has announced that the issues have been resolved.
All sessions have been invalidated and expired. All Angel users have to re-generate access token from the broker login page on Quantiply, if you want to run the algos
Users who din't get errors and issues, even for those users the sessions would have expired. Those users also have to re-generate access token ie. re-do broker login.
In short, all AngelOne users have to re-do broker login, if you want to continue using the algos today
Our recommendation:
Squaring off all positions manually, cancelling all pending orders and then Terminating the algos and closing for the day
Angel has announced that the issues have been resolved.
All sessions have been invalidated and expired. All Angel users have to re-generate access token from the broker login page on Quantiply, if you want to run the algos
Users who din't get errors and issues, even for those users the sessions would have expired. Those users also have to re-generate access token ie. re-do broker login.
In short, all AngelOne users have to re-do broker login, if you want to continue using the algos today
Our recommendation:
Squaring off all positions manually, cancelling all pending orders and then Terminating the algos and closing for the day
⚠️ AngelOne users: ⚠️
Order updates are getting delayed from Angel's side. Executed legs will show "Waiting" status
If the status of individual legs shows "Waiting" for more than 15 secs, then the positions will have to be managed manually.
Issue has been raised with AngelOne from our side. We will keep everyone updated
Order updates are getting delayed from Angel's side. Executed legs will show "Waiting" status
If the status of individual legs shows "Waiting" for more than 15 secs, then the positions will have to be managed manually.
Issue has been raised with AngelOne from our side. We will keep everyone updated
NSE has revised the quantity freeze limits for NIFTY and BANKNIFTY F&O contracts with effect from November 1
New Quantity Freeze Limits per order:
- Nifty: 1800 quantities / 36 lots
- BANKNIFTY: 900 quantities / 36 lots
New Quantity Freeze Limits per order:
- Nifty: 1800 quantities / 36 lots
- BANKNIFTY: 900 quantities / 36 lots
⚠️ AngelOne users: ⚠️
We have identified 2 issues with AngelOne:
1. Quantity passed to Angel is being taken as Lots and not as Quantity. Example: 150 quantity is being taken as 150 lots
2. Order tags that help differentiate between different orders placed by the algo are completely missing from their order book
Both these issues have been raised with Angel.
We have identified 2 issues with AngelOne:
1. Quantity passed to Angel is being taken as Lots and not as Quantity. Example: 150 quantity is being taken as 150 lots
2. Order tags that help differentiate between different orders placed by the algo are completely missing from their order book
Both these issues have been raised with Angel.
⚠️ AngelOne users: ⚠️
AngelOne has updated that the issue is resolved
You can share your algo page links with @abhishah33 and get your algos reset
AngelOne has updated that the issue is resolved
You can share your algo page links with @abhishah33 and get your algos reset
⚠️ AngelOne users: ⚠️
❗️Message from Angel "sessions have expired"
Broker login will have to be done again from the Broker Login page on Quantiply
Go to the broker login page, and click on "Re-generate access token" under your AngelOne client id.
Without doing broker login again, the algos will not work
❗️Message from Angel "sessions have expired"
Broker login will have to be done again from the Broker Login page on Quantiply
Go to the broker login page, and click on "Re-generate access token" under your AngelOne client id.
Without doing broker login again, the algos will not work
⚠️ AngelOne users: ⚠️
❗️Sessions expiring. Same issues with AngelOne today as well
In some cases re-login is also not helping
Issue raised with AngelOne
All other brokers working fine
❗️Sessions expiring. Same issues with AngelOne today as well
In some cases re-login is also not helping
Issue raised with AngelOne
All other brokers working fine
⚠️ AngelOne users: ⚠️
Solution: Re-generate the api key and secret from the https://smartapi.angelbroking.com/ and update them on the broker setup page of your AngelOne client id, and re-login.
This solution may help as tried by a few users.
Solution: Re-generate the api key and secret from the https://smartapi.angelbroking.com/ and update them on the broker setup page of your AngelOne client id, and re-login.
This solution may help as tried by a few users.
📣 New functionality 📣
SL order placement delay
Use case: Avoid spikes / Freak trades
Documentation:
https://quantiply.tech/documentation/advanced-settings/sl-order-placement-delay/
SL order placement delay
Use case: Avoid spikes / Freak trades
Documentation:
https://quantiply.tech/documentation/advanced-settings/sl-order-placement-delay/
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
One of our servers is facing network connectivity issues. Less than 5% of algos might get affected. You may or may not face any issues. Incase the algo shows a red dot (ie. algo not running), you can simply duplicate that algo and enable it and it will run just fine.
One of our servers is facing network connectivity issues. Less than 5% of algos might get affected. You may or may not face any issues. Incase the algo shows a red dot (ie. algo not running), you can simply duplicate that algo and enable it and it will run just fine.
📣 Important 📣
Limit Price Protection (LPP) mechanism & important settings.
Read here: https://quantiply.tech/documentation/important-topics/limit-price-protection-lpp-mechanism/
Limit Price Protection (LPP) mechanism & important settings.
Read here: https://quantiply.tech/documentation/important-topics/limit-price-protection-lpp-mechanism/
📣Here’s the clarification we’ve got from the exchange so far on Limit Price Protection (LPP)📣
Stoploss orders can be placed in advance even if they’re beyond +/- 40% or +/- 20 points from the Reference Price (RP). Limit or SL-Limit orders will not get rejected when you place them in advance or at the time of SL hit even if it is outside the LPP range.
The rejection comes only when the order is shot into the order book by the exchange. Meaning, only when the price crosses the Trigger Price, the order is shot into the order book ie. the order goes from ‘Pending’ state to ‘Open’ state. If at this point if the Limit price of your order is outside the LPP range, the order will get rejected.
We can see 2 scenarios playing out:
1. No rejection:
Price moves towards the stoploss slowly extending the LPP range along with it sufficiently to keep limit price of the exit order within the range and avoiding giving a rejection.
2. Order rejected:
Price spikes up or down, more than +/-40% or +/- 20 points in a few seconds and hitting stoploss, wherein the RP which is the average traded price of the last 30 seconds hasn’t changed in coherence with the price and the LPP range hasn’t extended yet. In the case of the rejection, the order can be squared off at the starting of the next 30 secs onwards, as by then the limit price may fall in the LPP range.
Currently, if the order is rejected, the order will have to be squared off manually. We will be implementing appropriate exit re-tries over the next 2-3 days
Stoploss orders can be placed in advance even if they’re beyond +/- 40% or +/- 20 points from the Reference Price (RP). Limit or SL-Limit orders will not get rejected when you place them in advance or at the time of SL hit even if it is outside the LPP range.
The rejection comes only when the order is shot into the order book by the exchange. Meaning, only when the price crosses the Trigger Price, the order is shot into the order book ie. the order goes from ‘Pending’ state to ‘Open’ state. If at this point if the Limit price of your order is outside the LPP range, the order will get rejected.
We can see 2 scenarios playing out:
1. No rejection:
Price moves towards the stoploss slowly extending the LPP range along with it sufficiently to keep limit price of the exit order within the range and avoiding giving a rejection.
2. Order rejected:
Price spikes up or down, more than +/-40% or +/- 20 points in a few seconds and hitting stoploss, wherein the RP which is the average traded price of the last 30 seconds hasn’t changed in coherence with the price and the LPP range hasn’t extended yet. In the case of the rejection, the order can be squared off at the starting of the next 30 secs onwards, as by then the limit price may fall in the LPP range.
Currently, if the order is rejected, the order will have to be squared off manually. We will be implementing appropriate exit re-tries over the next 2-3 days
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
Quantiply app not loading, we're checking the issue and resolving it asap
Quantiply app not loading, we're checking the issue and resolving it asap
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
There is a netowork connectivity issue at the data centres. We're trying the address the issue with the service provider asap
There is a netowork connectivity issue at the data centres. We're trying the address the issue with the service provider asap
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
Only the front end is affected. All algos are running fine and will run fine on backup systems. There will be no need to terminate the algos. Please monitor trades manually till connectivity issues are resolved for front end servers
Only the front end is affected. All algos are running fine and will run fine on backup systems. There will be no need to terminate the algos. Please monitor trades manually till connectivity issues are resolved for front end servers
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
You may not be able to Terminate the algos, as requests are not going from the front end to backend because of the front end connectivity issue. We're trying to re-direct the front end and resolve the issue asap. Please monitor trades on the terminal.
You may not be able to Terminate the algos, as requests are not going from the front end to backend because of the front end connectivity issue. We're trying to re-direct the front end and resolve the issue asap. Please monitor trades on the terminal.
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
The issue that is coming is being faced on the front end only, so front end will not load, even if it loads, the data is not loading as there is a connectivity issue at the data centre. You may see incorrect data. And you will also not be able to send any commands from the backend, like Terminate algo or Square off and terminate algo.
The servers running all algos are running on backup systems. The network connectivity issue may affect the algos also. As of now there is no issue with algos running, SLs are being placed properly, exits are happening correctly.
We are monitoring all other servers running algos as well.
The issue that is coming is being faced on the front end only, so front end will not load, even if it loads, the data is not loading as there is a connectivity issue at the data centre. You may see incorrect data. And you will also not be able to send any commands from the backend, like Terminate algo or Square off and terminate algo.
The servers running all algos are running on backup systems. The network connectivity issue may affect the algos also. As of now there is no issue with algos running, SLs are being placed properly, exits are happening correctly.
We are monitoring all other servers running algos as well.
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
Front end issues may continue as it is being stuffed with all the data that is being sent to it in broken data streams due to continued connectivity issues.
Algos are currently running fine on backup systems. We will update as soon soon as the front end issue is resolved. Given the scenario that the front end servers are facing today of broken data streams, it is possible that the front end may not function properly today.
As algos are already running on backups, trades will happen correctly, as long as backups also dont face connectivity issue. Chances of algos facing issues are very less. We are monitoring and we will update if we see any issues
Front end issues may continue as it is being stuffed with all the data that is being sent to it in broken data streams due to continued connectivity issues.
Algos are currently running fine on backup systems. We will update as soon soon as the front end issue is resolved. Given the scenario that the front end servers are facing today of broken data streams, it is possible that the front end may not function properly today.
As algos are already running on backups, trades will happen correctly, as long as backups also dont face connectivity issue. Chances of algos facing issues are very less. We are monitoring and we will update if we see any issues
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
All algos are running fine, so exits will happen correctly.
Incase exits are not happening, it can be because of an error or rejection from the broker or exchange. After your end time, refresh the broker terminal 2-3 times and check if all positions have exited. If not, then exit all positions manually and cancel all pending orders. Check and refresh the terminal 2-3 times before you exit or cancel manually
All algos are running fine, so exits will happen correctly.
Incase exits are not happening, it can be because of an error or rejection from the broker or exchange. After your end time, refresh the broker terminal 2-3 times and check if all positions have exited. If not, then exit all positions manually and cancel all pending orders. Check and refresh the terminal 2-3 times before you exit or cancel manually
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
INSTRUCTIONS TO CARRY OUT WITH RESPECT TO TODAY'S NETWORK ISSUE
For Intraday algos that ran today:
Case 1: If algo is showing Trade closed, then nothing to be done. It will run normally next Wednesday.
Case 2: If algo is showing Trade Active, then terminate the algo from the Quantiply dashboard. The algos showing Trade Active have not synced and updated the latest status correctly due to network connectivity bottleneck.
For Positional algos running from previous days, or today:
Positional algos will not run properly tomorrow as today's algo data is not synced and has to be completely reset. All positional algos have to be terminated today without fail, and positions have to be managed manually tomorrow.
INSTRUCTIONS TO CARRY OUT WITH RESPECT TO TODAY'S NETWORK ISSUE
For Intraday algos that ran today:
Case 1: If algo is showing Trade closed, then nothing to be done. It will run normally next Wednesday.
Case 2: If algo is showing Trade Active, then terminate the algo from the Quantiply dashboard. The algos showing Trade Active have not synced and updated the latest status correctly due to network connectivity bottleneck.
For Positional algos running from previous days, or today:
Positional algos will not run properly tomorrow as today's algo data is not synced and has to be completely reset. All positional algos have to be terminated today without fail, and positions have to be managed manually tomorrow.