ThinkWatch: a bulk CSV import can abort partway through

What happens

Importing a large CSV into ThinkWatch can stop partway through, leaving some of your rows imported and the rest silently missing — even when the file itself contains no duplicates.

What causes it

If the Plex or Jellyfin webhook happens to create a tracking entry for a show while your import is running, the import hits a conflict on that one row and abandons the entire remaining batch rather than skipping it.

So the trigger is a race with the automatic watch tracking, not a problem with your file.

Workaround

Run large imports when you are not actively watching anything, and re-run the import afterwards — already-imported rows are the ones that succeeded, so a second pass picks up what was missed.

Why it is Upstream

The fix belongs in Yamtrack, the application behind ThinkWatch. Reported upstream as FuzzyGrim/Yamtrack#1579 and accepted as a bug. This post tracks that fix.