Correct, which is why I was thinking of a season search being “smarter” than a multiple cutoff unmet/missing episode search but producing effectively the same result. That seems about right to you?
How would it be smarter?
On one hand it’d combine the missing and cutoff unmet searches into one, but it could also search for seasons that already have met the cutoff for every episode.
Ok. Then you can just implement the simple search for all cutoff unmet episodes and just put a warning somewhere that it would make a lot of api calls? That way at least the user has an option to do it or not.
That’s already done in v3… I mentioned that in my first response.
Right, I knew it will be in v3. It’s just that it isn’t released yet.