📣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.
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
All algos in 'READY' status will be terminated shortly.
Once algos are terminated, we will announce and you can refresh your Quantiply dashboard and check
All algos in 'READY' status will be terminated shortly.
Once algos are terminated, we will announce and you can refresh your Quantiply dashboard and check
⚠️ ❗️ANNOUNCEMENT❗️ ⚠️
All algos in 'READY' status have been terminated.
All systems will work normally tomorrow.
Please go through Instructions on Positional trades as mentioned here earlier: https://t.me/quantiply/420
All algos in 'READY' status have been terminated.
All systems will work normally tomorrow.
Please go through Instructions on Positional trades as mentioned here earlier: https://t.me/quantiply/420
⚠️ ❗️ANGEL ONE users ❗️⚠️
Order updates are missing and in some cases delayed for all orders.
Orders are getting placed, but algo is not receiving order updates, so the legs will show 'WAITING' status.
Square off positions manually or place SL orders manually or manage positions manually from the terminal
The issue has been raised with ANGEL, we will update once the issue is resolved
ALL OTHER BROKERS ARE WORKING FINE
Order updates are missing and in some cases delayed for all orders.
Orders are getting placed, but algo is not receiving order updates, so the legs will show 'WAITING' status.
Square off positions manually or place SL orders manually or manage positions manually from the terminal
The issue has been raised with ANGEL, we will update once the issue is resolved
ALL OTHER BROKERS ARE WORKING FINE
⚠️ ❗️ZERODHA users ❗️⚠️
There seems to be some issues with Zerodha, with order updates. Legs are in "WAITING" status
Order updates are not coming through.
Check if positions are open and place SL orders manually and manage positons manually
There seems to be some issues with Zerodha, with order updates. Legs are in "WAITING" status
Order updates are not coming through.
Check if positions are open and place SL orders manually and manage positons manually
⚠️ ❗️ZERODHA users ❗️⚠️
In most accounts manual orders from the Terminal are also not going through.
These are the 2 errors we're are seeing in the logs, coming from Zerodha
Error 1:
NetworkException:Request failed (kt-oms)
Error 2:
NetworkException:Order request timed out. Please check the order book and confirm before placing again.
In most accounts manual orders from the Terminal are also not going through.
These are the 2 errors we're are seeing in the logs, coming from Zerodha
Error 1:
NetworkException:Request failed (kt-oms)
Error 2:
NetworkException:Order request timed out. Please check the order book and confirm before placing again.
⚠️ ❗️ZERODHA users ❗️⚠️
All Zerodha users, disable all algos that are in READY status, till ZERODHA starts working fine. Their OMS is throwing errors and timeouts.
All Zerodha users, disable all algos that are in READY status, till ZERODHA starts working fine. Their OMS is throwing errors and timeouts.
⚠️ ❗️ZERODHA users ❗️⚠️
The issue is resolved according to a Zerodha executive
In reference to the order update issue: https://zerodha.com/marketintel/bulletin/337140/intermittent-issue-for-order-status-on-kite
The issue is resolved according to a Zerodha executive
In reference to the order update issue: https://zerodha.com/marketintel/bulletin/337140/intermittent-issue-for-order-status-on-kite
⚠️ ❗️ZERODHA users ❗️⚠️
Zerodha users can share the algo page links with @abhishah33 and get their algos reset.
Once algos are reset, disable the algo and enable it, and it will go into READY status and take positions.
Zerodha users can share the algo page links with @abhishah33 and get their algos reset.
Once algos are reset, disable the algo and enable it, and it will go into READY status and take positions.
⚠️ ❗️FINVASIA USERS ❗️⚠️
Getting an error:
16419 This error code will be returned for invalid data in the order packet
We're checking this with FINVASIA
Getting an error:
16419 This error code will be returned for invalid data in the order packet
We're checking this with FINVASIA
⚠️ ❗️FINVASIA USERS ❗️⚠️
Finvasia users can share algo page links with @abhishah33. Algos can be reset for now, once the issue is resolved from Finvasia's side we will informa and the algos can be fired up again
Finvasia users can share algo page links with @abhishah33. Algos can be reset for now, once the issue is resolved from Finvasia's side we will informa and the algos can be fired up again
⚠️ ❗️FINVASIA USERS ❗️⚠️
Issue is resolved
We're resetting algos, it may take a few minutes to reset everyones algos, please be patient, every ones algos will be reset
Issue is resolved
We're resetting algos, it may take a few minutes to reset everyones algos, please be patient, every ones algos will be reset