⚠️ ❗️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.
⚠️ ❗️ANGELONE USERS ❗️⚠️
Angel users are getting AB2001: Internal Error for order placement
We have updated Angel about it
Angel users are getting AB2001: Internal Error for order placement
We have updated Angel about it
QUANTIPLY users can now trade current week, weekly Options contracts & current month Futures contract of FINNIFTY
NOTE:
1. FINNIFTY weekly contracts expire on Tuesday every week.
2. For ZERODHA users,
- MIS orders are blocked in less liquid FINNIFTY strikes.
- NRML order type will work for all strikes.
- MARKET orders are only allowed for ATM option contracts, i.e. up to 1% ITM/OTM.
- LIMIT/SL-LIMIT orders allowed for all strikes.
3. For UPSTOX users,
- Only NRML allowed in all strikes. MIS orders are not allowed.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
4. For IIFL users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
5. For FINVASIA users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
6. For ANGELONE users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
7. The functionality of order conversion from Limit/SL-Limit to Limit//SL-Limit after N secs, which would be useful only for ZERODHA will be added in the coming days. It is advised to keep Limit/SL-Limit buffers on the higher side if you are trading with ZERODHA, so as to make sure the order is executed and conversion can be avoided till the functionality is added.
NOTE:
1. FINNIFTY weekly contracts expire on Tuesday every week.
2. For ZERODHA users,
- MIS orders are blocked in less liquid FINNIFTY strikes.
- NRML order type will work for all strikes.
- MARKET orders are only allowed for ATM option contracts, i.e. up to 1% ITM/OTM.
- LIMIT/SL-LIMIT orders allowed for all strikes.
3. For UPSTOX users,
- Only NRML allowed in all strikes. MIS orders are not allowed.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
4. For IIFL users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
5. For FINVASIA users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
6. For ANGELONE users,
- MIS & NRML, both order types allowed in all strikes.
- LIMIT/SL-LIMIT & MARKET orders allowed in all strikes.
7. The functionality of order conversion from Limit/SL-Limit to Limit//SL-Limit after N secs, which would be useful only for ZERODHA will be added in the coming days. It is advised to keep Limit/SL-Limit buffers on the higher side if you are trading with ZERODHA, so as to make sure the order is executed and conversion can be avoided till the functionality is added.
⚠️ ❗️ANGELONE USERS ❗️⚠️
Angel users are getting AB2001: Internal Error for order placement
We have updated Angel about it.
Check if legs that are giving this error are executed or not. If executed, place SL orders manually
Angel users are getting AB2001: Internal Error for order placement
We have updated Angel about it.
Check if legs that are giving this error are executed or not. If executed, place SL orders manually
⚠️ ❗️ALL USERS ❗️⚠️
For Wait & Trade entries, this week, use MARKET orders to enter. Limit orders placed in advance are giving circuit limit rejections and hence are not getting placed in some cases.
For Wait & Trade entries, this week, use MARKET orders to enter. Limit orders placed in advance are giving circuit limit rejections and hence are not getting placed in some cases.
⚠️ ❗️ALL USERS ❗️⚠️
For Wait & Trade entries, for tomorrow, use MARKET orders to enter. Limit orders placed in advance may give circuit limit rejections and trades will not be taken
For Wait & Trade entries, for tomorrow, use MARKET orders to enter. Limit orders placed in advance may give circuit limit rejections and trades will not be taken
⚠️ ❗️ANGELONE USERS ❗️⚠️
Some AngelOne users would be geting 502:Bad Gateway errors.
Check if legs that are giving this error are executed or not. If executed, place SL orders manually
You can get your algos reset from @abhishah33
Some AngelOne users would be geting 502:Bad Gateway errors.
Check if legs that are giving this error are executed or not. If executed, place SL orders manually
You can get your algos reset from @abhishah33