⚠️ ❗️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/
⚠️ ❗️FINVASIA users ❗️⚠️
Finvasia is throwing 503 errors for order placement, modification and fetching of order details. We have raised the issue with Finvasia.
Please check your algos to see if orders are placed correctly or not, and manage orders manually accordingly
Not all users will see errors. This is just a pre-emptive warning message of errors that we're seeing
Finvasia is throwing 503 errors for order placement, modification and fetching of order details. We have raised the issue with Finvasia.
Please check your algos to see if orders are placed correctly or not, and manage orders manually accordingly
Not all users will see errors. This is just a pre-emptive warning message of errors that we're seeing
⚠️ ❗️FINVASIA users ❗️⚠️
Finvasia has fixed the issue ✅
Finvasia has fixed the issue ✅
📣 NEW FUNCTIONALITY 📣
SL order placement delay for MTM SL
Use case: Avoid MTM SL exits on price spikes.
Documentation: https://quantiply.tech/documentation/advanced-settings/sl-order-placement-delay/#II._SL_order_placement_delay_f
SL order placement delay for MTM SL
Use case: Avoid MTM SL exits on price spikes.
Documentation: https://quantiply.tech/documentation/advanced-settings/sl-order-placement-delay/#II._SL_order_placement_delay_f
⚠️ ❗️ALL users ❗️⚠️
Any changes made to algos yesterday after 4:26 PM, will have to made again. An urgent security update was made on the database today morning, and some changes made to algos may have be rolled back for some users
Any changes made to algos yesterday after 4:26 PM, will have to made again. An urgent security update was made on the database today morning, and some changes made to algos may have be rolled back for some users
⚠️ ❗️ALL users ❗️⚠️
Live support on chat will be unavailable from 11 AM to 1:30 PM today
Live support on chat will be unavailable from 11 AM to 1:30 PM today
⚠️ ❗️ALL users ❗️⚠️
The platform will be down for the next 2 hours, from 11:30 PM to 1:30 AM for a system upgrade. Quantiply web application will not be available for the next 2 hours temporarily.
The platform will be down for the next 2 hours, from 11:30 PM to 1:30 AM for a system upgrade. Quantiply web application will not be available for the next 2 hours temporarily.
⚠️ ❗️FINVASIA users ❗️⚠️
Finvasia users would be getting an error SAF:Yel is down for order placement. We have notified Finvasia about this. We will update once the issue is resolved. Please execute and manage positions manually for now
Finvasia users would be getting an error SAF:Yel is down for order placement. We have notified Finvasia about this. We will update once the issue is resolved. Please execute and manage positions manually for now
⚠️ ❗️FINVASIA users ❗️⚠️
While we wait for the issue to get resolved, Finvasia users who have got errors for taking fresh positions, can share the algo page links with @abhishah33 so that the algos can be reset and re-used again.
Once the algo is reset, and only once the issue is resolved, one can disable the algo, and enable the algo again, and the algo will go into READY status and take fresh positions again.
Those whose algos are already running will have to manually exit the positions that have given the error
While we wait for the issue to get resolved, Finvasia users who have got errors for taking fresh positions, can share the algo page links with @abhishah33 so that the algos can be reset and re-used again.
Once the algo is reset, and only once the issue is resolved, one can disable the algo, and enable the algo again, and the algo will go into READY status and take fresh positions again.
Those whose algos are already running will have to manually exit the positions that have given the error
⚠️ ❗️FINVASIA users ❗️⚠️
If any algo is scheduled to run in the coming minutes, please disable the algos and do not take any fresh positions till there is a confirmation from Finvasia that the issue is resolved. Disable all new algos for the day
If any algo is scheduled to run in the coming minutes, please disable the algos and do not take any fresh positions till there is a confirmation from Finvasia that the issue is resolved. Disable all new algos for the day
⚠️ ❗️FINVASIA users ❗️⚠️
Finvasia issue resolved ✅
Please be careful and monitor if you are going to take new trades now.
Old open positions without any error should exit/re-enter/square off properly
Finvasia issue resolved ✅
Please be careful and monitor if you are going to take new trades now.
Old open positions without any error should exit/re-enter/square off properly
⚠️ ❗️ALL users ❗️⚠️
Some updates are being pushed. The website will be unavailable for sometime
Some updates are being pushed. The website will be unavailable for sometime
This media is not supported in your browser
VIEW IN TELEGRAM
📣 Run THURSDAY algos on WEDNESDAY📣
Here's a video on how to run your Thursday algos on Wednesday, as the upcoming Thursday 26th Jan is a trading holiday (Republic Day) and Wednesday 25th is the Expiry day
Here's a video on how to run your Thursday algos on Wednesday, as the upcoming Thursday 26th Jan is a trading holiday (Republic Day) and Wednesday 25th is the Expiry day
⚠️ ❗️For users using the PLACE IN ADVANCE option for SL orders ❗️⚠️
Some of the BANKNIFTY strikes on the PE side like 41500PE, 41400PE, 41300PE etc would be giving a circuit limit error while placing SL orders. If you have got this error, you will have to try and place the SL order manually or manage the position manually.
Inspite of multiple retries by the algo, the SL orders have still been giving this circuit limit error as it seems that the circuit limits had not been updated at the exchange.
This error may or may not come for the upcoming algos as the range would have been extended by the exchange by that time.
Some of the BANKNIFTY strikes on the PE side like 41500PE, 41400PE, 41300PE etc would be giving a circuit limit error while placing SL orders. If you have got this error, you will have to try and place the SL order manually or manage the position manually.
Inspite of multiple retries by the algo, the SL orders have still been giving this circuit limit error as it seems that the circuit limits had not been updated at the exchange.
This error may or may not come for the upcoming algos as the range would have been extended by the exchange by that time.
📣 RE-PLACEMENT OF EXIT ORDERS in case of:
(1) CIRCUIT LIMIT ERRORS
(2) MULTIPLE OTHER BROKER SPECIFIC ERRORS 📣
In the case of circuilt limit errors coming for placement of SL orders which are being placed in advance, and, multiple other broker specific errors coming for SL order placement due to which SL orders did not get placed, the algo will continously monitor the price and place the exit order (SL order) at the time the SL is hit ✅
The exit will happen normally in case any other type of exit like Target hit, MTM SL/Target or end time is triggered
The error message will continue to show on the algo page under the leg that got the error, even while algo is continously mornitoring the price of that leg. The error message will disappear only when a square off happens later in the day.
The re-placed SL orders will be placed as per the exit order type selected ie. Limit/SL Limit OR Market orders.
(1) CIRCUIT LIMIT ERRORS
(2) MULTIPLE OTHER BROKER SPECIFIC ERRORS 📣
In the case of circuilt limit errors coming for placement of SL orders which are being placed in advance, and, multiple other broker specific errors coming for SL order placement due to which SL orders did not get placed, the algo will continously monitor the price and place the exit order (SL order) at the time the SL is hit ✅
The exit will happen normally in case any other type of exit like Target hit, MTM SL/Target or end time is triggered
The error message will continue to show on the algo page under the leg that got the error, even while algo is continously mornitoring the price of that leg. The error message will disappear only when a square off happens later in the day.
The re-placed SL orders will be placed as per the exit order type selected ie. Limit/SL Limit OR Market orders.