Custom Channel sources are not part of this yet.
Oh OK. For a minute, I thought these were new checks introduced with this feature and displayed on the troubleshooting page, and I couldn't find them on mine. 
@eric @maddox Some feedback.. Found a movie scheduled that was previously imported.
687f1735-00b8-4b0b-a98a-b6f17315dac3
In Library:
Scheduled
@slampman You're right — this is a situation we'll be seeing over the next couple weeks.
2024/02/05 09:33:14.638499 [DVR] queued recording job for MV000024610000 @ Tue Feb 20 10:29:50PM on ch=[6039] (1708486190-52)
This was already set to record before the movie in your library was updated, so we didn't change the queued recording because it wasn't easy for us to deduce the intention.
Now that your imports have been updated, it will not happen for anything new that appears on the guide.
@mjitkop Thanks for reporting this. The movie in question had previously been skipped in a pass and we did not account for this scenario.
Please update to this pre-release:
and then go to the movie in question and select Manage -> Refresh Metadata and it should fix the issue with that movie.
1 Like
Ahhhh makes sense. Thanks for all the hard work 
1 Like
I have other movies that still show the blank gear icon so I guess I have to reprocess them all too.
I'm pretty sure I know the answer but I will ask the question anyway: no batch processing available?
If not, I will write a script to retrieve all the imported movies from my library and reprocess them.
I like this improvement. What happens if there are two versions of a movie and they have the same name? For example "The Taking of Pelham 123" One is the original and one is the remake.
You can differentiate movies with the same names by their release dates.
There seems to be three different versions in TMDB: The Taking of Pelham 123 — The Movie Database (TMDB) (themoviedb.org)
- "The Taking of Pelham One Two Three" (1974) => tmdb/8333
- "The Taking of Pelham One Two Three" (1998) => tmdb/314370
- "The Taking of Pelham 1 2 3" (2009) => tmdb/18487
1 Like
You can re-process everything with:
otherwise, there is a nightly task that refreshes the info that will handle it.
Will any of the actions taken (or not taken) be logged? I do see a Timeout that I assume is just a load issue?
[ERR] Failed to get movie info for tmdb/1832: Get "https://contentdb.fancybits.co/api/movies/tmdb/1832": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I would be interesting to see what files are being inspected and what actions are being taken but I like high verbosity logs and that might not be how others feel. 
2024/02/13 16:22:53.463494 [WRN] Server requested a slowdown while getting movie info for tmdb/493922: retrying in 2s
2024/02/13 16:23:12.181227 [WRN] Server requested a slowdown while getting movie info for tmdb/36243: retrying in 4s
2024/02/13 16:23:20.723889 [WRN] Server requested a slowdown while getting movie info for tmdb/36679: retrying in 6s
2024/02/13 16:23:34.143844 [WRN] Server requested a slowdown while getting movie info for tmdb/15766: retrying in 3s
2024/02/13 16:24:07.510472 [WRN] Server requested a slowdown while getting movie info for tmdb/393457: retrying in 1s
2024/02/13 16:24:16.621159 [WRN] Server requested a slowdown while getting movie info for tmdb/754: retrying in 2s
2024/02/13 16:24:26.035407 [WRN] Server requested a slowdown while getting movie info for tmdb/301875: retrying in 3s
2024/02/13 16:24:35.928905 [WRN] Server requested a slowdown while getting movie info for tmdb/8869: retrying in 4s
2024/02/13 16:24:46.956291 [WRN] Server requested a slowdown while getting movie info for tmdb/12920: retrying in 4s
2024/02/13 16:24:56.944874 [WRN] Server requested a slowdown while getting movie info for tmdb/11821: retrying in 5s
I'm not exactly sure what you're asking here. Can you rephrase?
It doesn't appear we have any specific load-related issues that I can see on our graphs, but it does look like we can add retries when we get timeouts like this, so this build should handle that better (and the logging for it).
We don't plan on logging every fetch that happens, but you should see the Activity showing the file that it is currently working on.
Just was wondering if that is OK ?
@Edwin_Perez Yep, all part of normal operation. I may remove the log messages eventually, but they're helpful right now to make sure that the backoff is working as intended.
Sure, something like "Found file XXXX, trying to match as IMDBYYYY." Or "Movie ZZZZ found in guide, matches File XXXX"
The goal to be knowing if my files are matching or not matching, being seeing and processed for matching or not being seen and processed for matching. There is the Experimental toggle for HTTP Logging so an additional toggle for File Match Logging could be considered similar.
On a tangent, a couple of 502s on Trakt. Only reporting for information:
2024/02/13 16:25:18.838501 [ERR] Failed to get movie info for tmdb/493828: error resolving trakt: tmdb: GET: https://api.trakt.tv/movies/fireplace-for-your-home-classic-edition-2008/ratings: 502 Bad Gateway: "error code: 502"
Just got a 500 error from the lookup
2024/02/14 12:43:26.087242 [IDX] Generating video index for file-29411: SciFi Fantasy\Terminator\Terminator - Dark Fate (2019).mkv
2024/02/14 12:43:28.501353 [ERR] ContentDB search error: Terminator: GET: https://contentdb.fancybits.co/api/movies/search/tmdb?q=Terminator: 500 Internal Server Error
2024/02/14 12:43:29.116482 [SCN] Imported movie #29411 SciFi Fantasy\Terminator\Terminator - Dark Fate (2019).mkv