Option & Expiration Availability
Bots notify you with an error or warning if a specific option leg or expiration are not available for your position. Here's why you receive these alerts, and how to avoid them.
Last updated
Bots notify you with an error or warning if a specific option leg or expiration are not available for your position. Here's why you receive these alerts, and how to avoid them.
Last updated
If the option leg or expiration you choose isn't available based on your settings, you'll receive a 'Requested option not found' error or a 'No option expiration available' warning.
For example, if you choose an expiration date that is 'exactly 30 days,' but there are no option contracts available for the underlying security, you'll receive a warning.
Similarly, when opening positions, you can specify detailed instructions for each leg, but there may not always be an option contract that meets your criteria.
If you select a specific criteria, such as 'Long call leg is $5 above short call leg exactly,' and there's no option contract that fits that description, you'll receive an error.
To avoid these errors and warnings, you can use the 'Opportunity is available' decision recipe to check if the exact position is available. If it's not available, the automation will stop without alerting you. This can help you avoid multiple notifications. Once the position type becomes available, the automation will continue as usual. It's worth noting that more option contracts typically become available as expiration approaches and demand for options increases.