⚠️ ❗️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
⚠️ ❗️IIFL USERS ❗️⚠️
A very small number of IIFL users would be getting an error Error: connect ECONNREFUSED 124.153.80.84:4005 for order placement and modification. This issue is from IIFL's side.
Solution:
Re-generate access token (re-login) from the Broker Login page on Quantiply immediately.
DM the algo page link to @abhishah33, if you require your algo to be reset
A very small number of IIFL users would be getting an error Error: connect ECONNREFUSED 124.153.80.84:4005 for order placement and modification. This issue is from IIFL's side.
Solution:
Re-generate access token (re-login) from the Broker Login page on Quantiply immediately.
DM the algo page link to @abhishah33, if you require your algo to be reset
What feature would you like to see on Quantiply next?
__Note: Both features are coming one after the other, no other features are going to be added before these 2 are launched.
__Note: Both features are coming one after the other, no other features are going to be added before these 2 are launched.
Anonymous Poll
33%
Target based re-entry/re-execute
67%
FINNIFTY weekly contracts
⚠️ ANNOUNCEMENT ⚠️
Reports generation will be limited to 1-2 days of reports at a time for the next 1-2 days as we're updating the functionality on the backend
Reports generation will be limited to 1-2 days of reports at a time for the next 1-2 days as we're updating the functionality on the backend
⚠️ ❗️ANGEL ONE users ❗️⚠️
There seems to be a delay with execution and order updates with Angel, we're checking the issue with them. Meanwhile if the orders are executed but the status of the legs is still showing Waiting, place SL orders manually
There seems to be a delay with execution and order updates with Angel, we're checking the issue with them. Meanwhile if the orders are executed but the status of the legs is still showing Waiting, place SL orders manually
⚠️ ❗️ANGEL ONE users ❗️⚠️
Angel’s master contracts endpoint of the API is failing since morning. As of now, contracts aren’t being fetched. AngelOne users will not be able to trade today till the issue is resolved
Angel’s master contracts endpoint of the API is failing since morning. As of now, contracts aren’t being fetched. AngelOne users will not be able to trade today till the issue is resolved
⚠️ ❗️ANGEL ONE users ❗️⚠️
AngelOne users can disable all algos for now. Once the issue is resolved, we will inform and you can enable the algos again
AngelOne users can disable all algos for now. Once the issue is resolved, we will inform and you can enable the algos again
⚠️ ❗️ANGEL ONE users ❗️⚠️
AngelOne Master Contracts are fetched, you can now start trading. Users who have terminated algos can DM @abhishah33 the algo page links to get the algos reset
AngelOne Master Contracts are fetched, you can now start trading. Users who have terminated algos can DM @abhishah33 the algo page links to get the algos reset
⚠️ ❗️ANGEL ONE users ❗️⚠️
Orders are going into 'WAITING' status, and orders are not being placed. The issue with AngelOne is still there. Once resolved we will update
Orders are going into 'WAITING' status, and orders are not being placed. The issue with AngelOne is still there. Once resolved we will update
⚠️ ❗️ANGEL ONE users ❗️⚠️
AngelOne users will not be able to trade today, as the algos will keep showing WAITING status due to the MasterContracts issue.
Angel users can trade manually
AngelOne users will not be able to trade today, as the algos will keep showing WAITING status due to the MasterContracts issue.
Angel users can trade manually
📣 NEW FEATURE 📣
TARGET based RE-ENTRY / RE-EXECUTE
You can now re-enter positions that have hit the Target using,
1. Re-Cost( re-enter when the price comes back to entry price).
2. Re-Execute (re-enter immediately after the Target hits).
3. MTM Target based re-entry.
Note:
1. Target based re-entry/re-execute functionality works exactly like the Stoploss based re-entry/re-execute.
2. Target based Re-Entry/Re-Execute and Stoploss based Re-Entry/Re-Execute can both be used together for each individual legs and also for MTM Target, all in the same algo.
TARGET based RE-ENTRY / RE-EXECUTE
You can now re-enter positions that have hit the Target using,
1. Re-Cost( re-enter when the price comes back to entry price).
2. Re-Execute (re-enter immediately after the Target hits).
3. MTM Target based re-entry.
Note:
1. Target based re-entry/re-execute functionality works exactly like the Stoploss based re-entry/re-execute.
2. Target based Re-Entry/Re-Execute and Stoploss based Re-Entry/Re-Execute can both be used together for each individual legs and also for MTM Target, all in the same algo.
📣 NEW SETTING for TARGET based RE-ENTRY / RE-EXECUTE
This setting allows for a common count for re-entry/re-execute between Target and Stoploss re-entries or a separate individual count for Target based re-entry/re-execute and a separate count for Stoploss based re-entry/re-execute.
There are 2 options to specify the max number of times that you want the re-entry/re-execute to happen for Target hit and/or Stoploss hit:
1. Individual
2. Common (As per Stockmock.in logic)
Read detailed documentation here: https://quantiply.tech/documentation/advanced-settings/re-entry-max-count-type/
This setting allows for a common count for re-entry/re-execute between Target and Stoploss re-entries or a separate individual count for Target based re-entry/re-execute and a separate count for Stoploss based re-entry/re-execute.
There are 2 options to specify the max number of times that you want the re-entry/re-execute to happen for Target hit and/or Stoploss hit:
1. Individual
2. Common (As per Stockmock.in logic)
Read detailed documentation here: https://quantiply.tech/documentation/advanced-settings/re-entry-max-count-type/
⚠️ ❗️ZERODHA users ❗️⚠️
For some Zerodha users orders are not getting placed and are getting the error error:TokenException:Incorrect `api_key` or `access_token`
Solution:
1. Re-do broker login from the Broker Login page (ie. re-generate access token)
2. Once broker login is re done, share the algo page links with @abhishah33 to reset the algos
3. Once algos are reset, you can disable the algos, wait for 5 secs and enable the algo again, and it will take positions without errors
For some Zerodha users orders are not getting placed and are getting the error error:TokenException:Incorrect `api_key` or `access_token`
Solution:
1. Re-do broker login from the Broker Login page (ie. re-generate access token)
2. Once broker login is re done, share the algo page links with @abhishah33 to reset the algos
3. Once algos are reset, you can disable the algos, wait for 5 secs and enable the algo again, and it will take positions without errors
⚠️ ❗️ANGELONE users ❗️⚠️
AngelOne users need to do the broker login (generate access token) using MPIN only. Password will not work, only MPIN will work tomorrow onwards.
If you haven’t created an MPIN for your AngelOne account yet, then it can be done on https://trade.angelone.in/
AngelOne users need to do the broker login (generate access token) using MPIN only. Password will not work, only MPIN will work tomorrow onwards.
If you haven’t created an MPIN for your AngelOne account yet, then it can be done on https://trade.angelone.in/