⚠️ Wait & Trade data is now being displayed properly on the UI. Refresh the page to see the data ⚠️
⚠️ Update: Wait & Trade + RE EXECUTE + Square off all legs ⚠️
When Wait & Trade + RE EXECUTE + Square off all legs is configured together, note that the Wait & Trade condition will get applied to the re-entry orders as well. Which means, that after the SL is hit, the whole entry logic is re-executed. Which is - strike selection, calculating entry price after applying wait & trade condition to the reference price.
When Wait & Trade + RE EXECUTE + Square off all legs is configured together, note that the Wait & Trade condition will get applied to the re-entry orders as well. Which means, that after the SL is hit, the whole entry logic is re-executed. Which is - strike selection, calculating entry price after applying wait & trade condition to the reference price.
⚠️ For IIFL users: Some open positions have been closed by IIFL, with error message: "16795 : Order cancelled due to voluntary close out.". We're checking with IIFL what this means. Meanwhile if there are any naked open positions, please square them off manually⚠️
⚠️ For IIFL users: As per IIFL, only pending Limit/SL Limit orders are cancelled. Open positions are still open and will stay open.
Option 1: You can manually place the SL orders that got cancelled directly from the XTS terminal, and let the algo run as it is
Option 2: If trailing and combined premium exits are involved then you can Square off all positions and terminate the algo⚠️
SAFEST OPTION: Option 2
Option 2 will help avoid any kind of double orders to get triggered, 1 that is manual and 1 that is triggered by the algo. This is specific to certain scenarios and not all
Option 1: You can manually place the SL orders that got cancelled directly from the XTS terminal, and let the algo run as it is
Option 2: If trailing and combined premium exits are involved then you can Square off all positions and terminate the algo⚠️
SAFEST OPTION: Option 2
Option 2 will help avoid any kind of double orders to get triggered, 1 that is manual and 1 that is triggered by the algo. This is specific to certain scenarios and not all
⚠️ For IIFL users: For algos where Entry order type and Exit order type is MARKET, will not be affected and those algos dont need to be square off and terminated ⚠️
⚠️ As one would notice, for BANKNIFTY strikes above 40000 and below 30900 occur in multiples of 500, instead of 100, for most weekly expiry contracts for this month and the upcoming month.
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens as the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
SOLUTION:
By Wednesday evening, we will be giving an option to enter 500 multiple strikes only, in BANKNIFTY while configuring the leg-wise strike selection. This will enable positions to be taken in strikes that occur in multiples of 500 while being closest to the configured strike level like OTM20 or OTM21 and so on. A detailed explnation of this will be shared on Wednesday when this functionality is published. ⚠️
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens as the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
SOLUTION:
By Wednesday evening, we will be giving an option to enter 500 multiple strikes only, in BANKNIFTY while configuring the leg-wise strike selection. This will enable positions to be taken in strikes that occur in multiples of 500 while being closest to the configured strike level like OTM20 or OTM21 and so on. A detailed explnation of this will be shared on Wednesday when this functionality is published. ⚠️
This media is not supported in your browser
VIEW IN TELEGRAM
📣 New Functionality: Select 500 / 100 multiple strikes in Banknifty & Nifty respectively while configuring LEGS.📣
While configuring the Legs in the algo, one can choose the option to select and take positions only in strikes that occur in the 500/100 multiples
[continued...]
While configuring the Legs in the algo, one can choose the option to select and take positions only in strikes that occur in the 500/100 multiples
[continued...]
📣 New Functionality: Select 500 / 100 multiple strikes in Banknifty & Nifty respectively while configuring LEGS. 📣
THE ISSUE:
As one would notice, for BANKNIFTY strikes above 40000 and below 30900 occur in multiples of 500, instead of 100, for most weekly expiry contracts for this month and the upcoming month.
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens because the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
THE SOLUTION:
The solution to this issue would be to try and select only those active strikes which occur only in the multiples of 500. And for the algo to do that, we have added an optional functionality to select only 500 or 100 multiple strikes for Banknifty and Nifty respectively.
So, while configuring the Legs in the algo, one can choose the option to select only 500/100 multiple strikes.
Example:
Say the Banknifty spot is currently at 38319, and one of the legs configured in the algo is OTM 20. This means that the ATM is 38300 and the OTM 20 is 40300.
Since beyond the 40000 strike, only strikes that are active occur in the multiple of 500, hence the next active strike after 40000 is 40500. But the algo will not take entries, as, based on the Leg configured, the strike selected is 40300, which is inactive.
In this case, if the option to select 500/100 multiple strikes is selected while configuring the leg, the algo will automatically take positions in the strike which is closest to 40300 but at the same time in the direction which is closer to the ATM.
Hence the algo, will take the entry in 40000 instead of shooting an order for 40300, as 40000 is the closest strike to 40300 and is also closer to the ATM than 40300 or even 40500.
HOW TO CONFIGURE THIS SETTING?
Click on the symbol selection dropdown menu > click on Legs > select the strike & select the option 500/100 multiple under Specific strike selection option. Once selected, click Done, and click Save to save the algo settings.
THE ISSUE:
As one would notice, for BANKNIFTY strikes above 40000 and below 30900 occur in multiples of 500, instead of 100, for most weekly expiry contracts for this month and the upcoming month.
Since the 'in-between' 100 multiple strikes are not available to trade, most of the far OTM configurations like OTM20 and beyond would not be immediately taking positions at the start time as they fall on one of the 'in-between' 100 multiple strikes.
As currently there is no indication on the Quantiply UI to display if your configured strikes falls in one of the non tradable 'in-between' strikes, some of you have raised the issue of positions not being taken and algo being in READY status even after crossing the start time. This happens because the algo would not take any positions unless all configured strikes are available to trade and have a continuously updating ticker.
THE SOLUTION:
The solution to this issue would be to try and select only those active strikes which occur only in the multiples of 500. And for the algo to do that, we have added an optional functionality to select only 500 or 100 multiple strikes for Banknifty and Nifty respectively.
So, while configuring the Legs in the algo, one can choose the option to select only 500/100 multiple strikes.
Example:
Say the Banknifty spot is currently at 38319, and one of the legs configured in the algo is OTM 20. This means that the ATM is 38300 and the OTM 20 is 40300.
Since beyond the 40000 strike, only strikes that are active occur in the multiple of 500, hence the next active strike after 40000 is 40500. But the algo will not take entries, as, based on the Leg configured, the strike selected is 40300, which is inactive.
In this case, if the option to select 500/100 multiple strikes is selected while configuring the leg, the algo will automatically take positions in the strike which is closest to 40300 but at the same time in the direction which is closer to the ATM.
Hence the algo, will take the entry in 40000 instead of shooting an order for 40300, as 40000 is the closest strike to 40300 and is also closer to the ATM than 40300 or even 40500.
HOW TO CONFIGURE THIS SETTING?
Click on the symbol selection dropdown menu > click on Legs > select the strike & select the option 500/100 multiple under Specific strike selection option. Once selected, click Done, and click Save to save the algo settings.
📣 Move SL to Cost issue for Positional trades FIXED: 📣
Earlier:
For Positional trades, if one of the sides has already Moved it's SL to Cost, the next morning, the SL of that side gets revised back to the original SL instead of SL to Cost.
After the FIX:
The next day, the SL applied will be at Cost, instead of the Original SL.
Earlier:
For Positional trades, if one of the sides has already Moved it's SL to Cost, the next morning, the SL of that side gets revised back to the original SL instead of SL to Cost.
After the FIX:
The next day, the SL applied will be at Cost, instead of the Original SL.
⚠️ IMPORTANT ⚠️
Huge spikes and slippages on the PE side today. Traders using Market orders for exits will get huge slippages. Inspite of repeat suggestions to use Limit/SL Limit orders, even some experienced traders are still using Market orders for exits in some cases.
Please use Limit/SL Limit orders for exits. Gamma spikes mostly occur on expiry days. It may be resonable to set N secs on Limit/SL Limit orders to a higher number to allow the price to cool down (ONLY for expiry days where gamma spikes are a regular occurence). A higher value like N=120 secs (for Limit/SL Limit order) may help, but comes with a risk.
Any suggestions to reduce slippages on spikes are welcome. But with suggestions, recommendations on how to address tail end risk is also required.
Huge spikes and slippages on the PE side today. Traders using Market orders for exits will get huge slippages. Inspite of repeat suggestions to use Limit/SL Limit orders, even some experienced traders are still using Market orders for exits in some cases.
Please use Limit/SL Limit orders for exits. Gamma spikes mostly occur on expiry days. It may be resonable to set N secs on Limit/SL Limit orders to a higher number to allow the price to cool down (ONLY for expiry days where gamma spikes are a regular occurence). A higher value like N=120 secs (for Limit/SL Limit order) may help, but comes with a risk.
Any suggestions to reduce slippages on spikes are welcome. But with suggestions, recommendations on how to address tail end risk is also required.
📣 New feature: Download reports / Trade Journal ⚡️
You can now export historic trade details and maintain a journal of all the trades done on Quantiply.
I. How to download reports:
Click on your profile section and go to the Reports section. Select a date or a date range and download the reports.
II. Important points:
1. Reports can be generated for a maximum of 7 days at a time.
2. Current trading day’s reports can be downloaded only after market hours, on the same day, and NOT during market hours.
3. If an algo is reset for any reason after taking positions or encountering errors, the previous trade details (in case any trades had taken place before the algo was reset) will be lost and not recorded in the reports.
4. For Positional trades, the exit trade details will show in the reports only after the trades have been squared off, till then, only the entry trades will show in the report and the exit trade details will be blank.
5. For any change in the client id/broker, algo name, or algo configuration, the latest updated client id/broker, algo name, or algo configuration will reflect in the reports, and NOT the client id/broker, algo name, or algo configuration that was used at the time and day the algo had run historically. This will be the case only for algos that were run before 30th August 2022.
For algos run after 30th August 2022, the client id/broker, algo name, or algo configuration that were used in the algo, will be the ones that will reflect in the downloaded reports, even if the client id/broker, algo name, or algo configuration is updated later.
You can now export historic trade details and maintain a journal of all the trades done on Quantiply.
I. How to download reports:
Click on your profile section and go to the Reports section. Select a date or a date range and download the reports.
II. Important points:
1. Reports can be generated for a maximum of 7 days at a time.
2. Current trading day’s reports can be downloaded only after market hours, on the same day, and NOT during market hours.
3. If an algo is reset for any reason after taking positions or encountering errors, the previous trade details (in case any trades had taken place before the algo was reset) will be lost and not recorded in the reports.
4. For Positional trades, the exit trade details will show in the reports only after the trades have been squared off, till then, only the entry trades will show in the report and the exit trade details will be blank.
5. For any change in the client id/broker, algo name, or algo configuration, the latest updated client id/broker, algo name, or algo configuration will reflect in the reports, and NOT the client id/broker, algo name, or algo configuration that was used at the time and day the algo had run historically. This will be the case only for algos that were run before 30th August 2022.
For algos run after 30th August 2022, the client id/broker, algo name, or algo configuration that were used in the algo, will be the ones that will reflect in the downloaded reports, even if the client id/broker, algo name, or algo configuration is updated later.
📣 UPDATE: Add additional algos OR Upgrade plans during market hours 📣
You can now add additional algos or upgrade plans during market hours. Once the algo limit is increased or plans are upgraded, you will immediately have access to the additional algos.
Reduction in the number of algos subscribed or downgrade of plans will take effect after market hours only.
You can now add additional algos or upgrade plans during market hours. Once the algo limit is increased or plans are upgraded, you will immediately have access to the additional algos.
Reduction in the number of algos subscribed or downgrade of plans will take effect after market hours only.
⚠️ ZERODHA Users: Alert ⚠️
2 errors coming from Zerodha for order placement and modification
1. "Server not ready"
2. "The exchange connection (adapter) did not accept the order. Please retry"
Monitor your trades. Some trades may have to be managed manually
2 errors coming from Zerodha for order placement and modification
1. "Server not ready"
2. "The exchange connection (adapter) did not accept the order. Please retry"
Monitor your trades. Some trades may have to be managed manually
⚠️ IIFL Users: Alert ⚠️
IIFL accounts getting the error - 16795 : Order cancelled due to voluntary close out.
We're checking the reason for this error with IIFL
IIFL accounts getting the error - 16795 : Order cancelled due to voluntary close out.
We're checking the reason for this error with IIFL
⚠️ IIFL Users: Alert ⚠️
Message from IIFL:
"Orders were cancelled by exchange
Please place orders now and also check your open orders for Stoploss"
For those who want to get their algos reset, DM us the algo page link and we will reset the algo
For those who are running simple strategies can just place manual SL orders in the terminal
Message from IIFL:
"Orders were cancelled by exchange
Please place orders now and also check your open orders for Stoploss"
For those who want to get their algos reset, DM us the algo page link and we will reset the algo
For those who are running simple strategies can just place manual SL orders in the terminal
⚠️ FINVASIA Users: Alert ⚠️
FINVASIA accounts getting the error - 16795 : Order cancelled due to voluntary close out.
FINVASIA accounts getting the error - 16795 : Order cancelled due to voluntary close out.
FINVASIA - Order cancelled due to voluntary close out
ISSUE RESOLVED!
Next steps:
Option 1: Place SL orders manually
Option 2: Square off all open positions and get algos reset via DM and re-take positions
ISSUE RESOLVED!
Next steps:
Option 1: Place SL orders manually
Option 2: Square off all open positions and get algos reset via DM and re-take positions
⚠️ FINVASIA Users: Alert ⚠️
FINVASIA has been alerted that orders are still getting rejected. We will share an update asap
FINVASIA has been alerted that orders are still getting rejected. We will share an update asap
📣 New feature 📣
Underlying based Entries & Exits ⚡️
This functionality allows entries and exits to be taken based on the movement of the underlying. Currently, this feature will work only with Nifty and Banknifty spot price as underlying.
There are 3 parts to this feature:
1. Wait & Trade entries based on Underlying.
2. Underlying based SL.
3. Underlying based Target.
📝 Detailed documentation: https://quantiply.tech/documentation/features-trade-logic/underlying-based-entries-and-exits
Underlying based Entries & Exits ⚡️
This functionality allows entries and exits to be taken based on the movement of the underlying. Currently, this feature will work only with Nifty and Banknifty spot price as underlying.
There are 3 parts to this feature:
1. Wait & Trade entries based on Underlying.
2. Underlying based SL.
3. Underlying based Target.
📝 Detailed documentation: https://quantiply.tech/documentation/features-trade-logic/underlying-based-entries-and-exits
📣 New functionality 📣
Enable or Disable multiple algos⚡️
Now you can Enable or Disable multiple algos at the same time.
Note: When multiple algos are enabled using this option, each algo is enabled sequentially and not in parallel all together. So it can take a few seconds for all algos to get enabled.
Enable or Disable multiple algos⚡️
Now you can Enable or Disable multiple algos at the same time.
Note: When multiple algos are enabled using this option, each algo is enabled sequentially and not in parallel all together. So it can take a few seconds for all algos to get enabled.