We are currently configuring a Nifty options strategy on the FYERS FIA automation platform. We require a conditional rule to dynamically switch between Current-Month and Next-Month expiries based on the remaining days to expiry (e.g., Use current-month when days to expiry > 15, and next-month when days to expiry ≤ 15).
However, current node constraints do not permit range comparisons or numerical output for days to expiry.
3. Technical Details & Limitations Encountered
-
“Days to Expiry” Node Limitation:
-
The current Days to Expiry node only accepts a single exact number match (e.g., exactly 15 days). It does not provide operators like “Greater than (>)”, “Less than (<)”, or “Between (Range)”.
-
To achieve a >15 days check, we would have to manually chain individual exact-day checks (16, 17, 18… up to 35+ days), which duplicates entry and monitoring branches, bloating the canvas to an unmanageable size.
-
-
Query Builder Limitation:
- The Query Builder and available data sources (Option Chain, Realtime Data, Candles, Get Symbol, etc.) do not expose Expiry Date or Days to Expiry as a usable numeric variable that can be evaluated in an expression (e.g.,
Days_Remaining >= 15).
- The Query Builder and available data sources (Option Chain, Realtime Data, Candles, Get Symbol, etc.) do not expose Expiry Date or Days to Expiry as a usable numeric variable that can be evaluated in an expression (e.g.,
4. Proposed Enhancement / Feature Request
To make advanced multi-expiry options strategies viable on the FIA platform, we kindly request FYERS to consider the following platform upgrades:
-
Enhanced Operators in “Days to Expiry” Node: Add comparative operators (
>,<,>=,<=,Between) rather than restricting checks to a single exact integer. -
Expose Expiry Variables in Query Builder: Make contract expiry dates and remaining days to expiry accessible as numeric parameters within the Query Builder so custom expression comparisons can be built.
Thank you for your assistance. Please let us know if there is an existing workaround or if this can be escalated to the product/development team.