[Logging] MDBList "episode no-id" entries lack show and episode context for troubleshooting

[Lentzeris]

Summary

When an MDBList push job completes, the log shows "not found" items. While entries with a TMDB ID (e.g., movie tmdb:369300, show tmdb:95391) can be identified by looking up that ID, the episode no-id S# entries provide no way to identify which show or specific episode failed to sync.

Example Log Output

MDBList push job 213: 9 item(s) not found on MDBList: movie tmdb:369300; episode no-id S6; episode no-id S3; episode no-id S6; episode no-id S2; episode no-id S9; episode no-id S10; show tmdb:95391; episode no-id S1

The Problem

The episode no-id S# entries are impossible to troubleshoot because the user cannot tell:

• Which show these episodes belong to
• Which specific episode numbers within that season failed
• Whether this is a metadata issue, a missing ID, or something else

Without this context, users cannot:

• Check if the episode exists on MDBList
• Verify the metadata in Scrob
• Manually refresh or fix the specific item

Scope

I've only observed this with MDBList so far, but the same logging issue could potentially affect other services like Simkl if they encounter similar "not found" episodes. The fix should ideally cover all external sync services where this type of logging is used.

Expected Behavior

When logging "not found" for an episode, include enough context to identify the media item, ideally using the show title or the original media identifier (e.g., Jellyfin item name or ID).

Suggested Fix

For episode no-id entries, log either:

1. The Jellyfin item name/path that Scrob is trying to sync, or
2. The show title + season number + episode number from Scrob's local database

This would allow users to identify which media file or entry is causing the issue and take appropriate action (e.g., checking metadata, refreshing the item, or reporting to MDBList).

[Lentzeris]

I appreciate the update with commit b0decea, but unfortunately this change doesn't help with troubleshooting.

For an episode no-id S1 error, the log now shows something like this:

episode no-id S1 (possibly: Lost, Silo, Show 3, Show 4, ....[every single show in MDBList's database that has a Season 1])

Since every TV show has a Season 1, this list is essentially every single show in the database. It provides no way to identify which specific show actually failed to sync.

The helpful information would be:

1. The show title that Scrob was trying to sync
2. The episode number (e.g., S01E03)
3. The Jellyfin item name or path as a fallback

I guess this information is already available in Scrob's local database – it just needs to be included in the log.

[ellite]

The only think mdblist returns as failed is "Season 1". So, I'm listing everything with season 1 that was on the bulk of the sync.
Unfortunately, I don't have a way to be more precise.

[Lentzeris]

I understand that MDBList only returns "Season 1" in its response. But Scrob already has the full context before it sends the request – the show title, season, and episode number are all in the payload Scrob builds.

The log doesn't need to recover anything from MDBList's response. It just needs to show what Scrob sent. That information exists locally in Scrob's database and the sync payload.

For example, Scrob already knows it's trying to sync "The Walking Dead" S01E03. The log should just say that, rather than trying to guess from MDBList's minimal response.

The data is there – it just needs to be included in the log.

[Lentzeris]

Looking at core/mdblist.py, I can see that the _push function already builds the full batch payload before sending it to MDBList. This batch contains the show title, season, and episode number for every item.

The _index_episode_shows function you added already pulls data from this batch to recover context after the fact. This is what generates the list of "possible" shows.

Instead of trying to match MDBList's minimal error response back to the request, could we just log the request details directly? The batch already has everything we need:

1. Show title
2. Season number
3. Episode number
4. TMDb ID (if available)

The log could simply show what Scrob sent, rather than guessing from MDBList's response. This would be more reliable and much more helpful for troubleshooting.