Plain-language troubleshooting

A title says episodes are missing

Missing means Omakase cannot currently prove the expected inventory.

Check:

1. the AniList season and expected episode count;
2. whether the release uses unusual absolute numbering;
3. the latest candidate rejection reasons;
4. source availability;
5. provider acceptance;
6. local file readability;
7. whether the scheduler has another check planned.

Do not lower identity, subtitle, or playback rules just to make the card green.

Some sources are unavailable

This means at least one configured source failed while another source could still work. Confirm the catalog service itself is healthy, then inspect each source receipt.

Temporary upstream errors should not disable successful sources. Correct punctuation-heavy or alias-poor searches only through the supported title-normalization path.

Plex cannot see the files

Confirm the same bytes through all three path views:

• host path;
• Omakase container path;
• Plex container or host path.

Then confirm the Plex section uses the Plex-visible path and the scoped scan completed. Do not run a whole-library refresh until the path mismatch is understood.

Subtitles exist but the title is not ready

A subtitle filename or language tag is not enough. Confirm it is:

• an actual selectable stream;
• English when English readiness is required;
• embedded in the exact media release, or explicitly fingerprinted and sync-verified as an external fallback.

A burned-in release must be labelled as burned-in and is used only after eligible switchable candidates are exhausted.

Playback fails after a provider remount

The provider path may look healthy on the host while an existing container still holds a stale mount. Refresh the mount and its consumer containers in the documented order for your deployment, then rerun the acquisition dry-run.

Do not restart only one mount service when dependent containers retain the disconnected filesystem view.

A scheduled check appears stuck

Confirm no sync process is running. Capture the current revision and latest receipt, then make an online SQLite backup.

Use the release-provided owner-matched stale-lease recovery function. Do not edit the scheduler table manually.

Doctor reports a VPN failure

Keep the qBittorrent profile stopped until Gluetun is healthy and Doctor proves:

• tunnel device and capability;
• kill switch;
• shared network namespace;
• exact qBittorrent binding;
• no independent host port.

Omakase never treats ordinary host networking as a fallback VPN.

The right repair order

1. Stop mutation.
2. Capture revision, receipt, logs, and Doctor result.
3. Back up SQLite and affected configuration.
4. Repair one boundary.
5. Rerun the narrow plan or Doctor check.
6. Apply only the reviewed hash.
7. Verify Plex and playback.
8. Preserve the new receipt and rollback reference.