Rotten Tomatoes filter not working for automatic/scheduled run
Opened this issue · 2 comments
I've added a "rotten_tomatoes" score filter of 75 for "automatic". I've made sure to add the OMDb API Key and have tested that the filter works via manual CLI. It just seems to ignore the filter when running automatically on the schedule.
Here's the interesting part - When I use:
traktarr run --run-now
It DOES correctly apply the rotten_tomatoes score filter.
System Information
- Traktarr Version: 1.2.5
- Operating System: Ubuntu Server 18.04.3 LTS
traktarr movies -t trending -rt 80
Isn't working either. You get this on every entry found:
2020-03-07 21:30:35,383 - INFO - helpers.omdb - does_movie_have_min_req_rt_score - SKIPPING: 'Baby Driver (2017)' because a Rotten Tomatoes score could not be found. 2020-03-07 21:30:36,496 - INFO - helpers.omdb - does_movie_have_min_req_rt_score - SKIPPING: 'Trolls (2016)' because a Rotten Tomatoes score could not be found. 2020-03-07 21:30:37,121 - INFO - helpers.omdb - does_movie_have_min_req_rt_score - SKIPPING: 'It (2017)' because a Rotten Tomatoes score could not be found. 2
Still having this issue with latest container version from eafxx/traktarr.
Im sure this 'test' movie has a rotten tomatoes score.