About transfer-failed-retry
A structured retry procedure for failed MoviePilot transfers, intended for operators correcting and retrying transfer records. It requires checking record ownership, source availability, media identity, and a preview before using the appropriate durable-task or legacy flow.
Key features
- 01Inspect history records and task context
- 02Check source files and storage status
- 03Verify media identity and episode details
- 04Preview transfer plans before submission
- 05Use distinct durable and legacy flows
- 06Report outcomes and blockers accurately
Use cases
- 01Retry after correcting a media identification
- 02Replan a durable failure with no file effects
- 03Process a failed record explicitly marked legacy
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ jxxghp/ moviepilot --skill transfer-failed-retryAfter installing, type/transfer-failed-retryin Claude Code to confirm it loaded.
Details
From the project READMETransfer Failed Retry
Use structured moviepilot_api operations only; discover their current schemas.
Required Flow
- Inspect every exact requested history ID. Record source/storage, destination, mode, identity, season/episode, status, error, and durable task context. Treat unknown task ownership as durable, and never act on another record.
- Verify source availability with
storage.list. Stop for missing files, storage/permission/configuration faults, manual review, uncertain effects, or exhausted retry budgets. Do not delete targets or change global rules. - Analyze the filename and error. Verify identity with
media.recognizeormedia.search, and check TV season/episode withmedia.detailormedia.seasons. Do not reuse a wrong failed identification unchanged.Season 2 - 03requires verifying S02E03 rather than assuming S01. Group only proven shared identities; verify each file's season/episode. - Preview with
transfer.fileandpreview=trueusing the original source, destination, mode, and verified identity and season/episode. Inspect the preview before submitting any correction. - For durable records, use
transfer.history.replanwith the exact history ID, originaltask_idandsettlement_revisionfrom the supplied context, verifiedmedia_source,media_id,media_type(movie/tv), and optionalseason/episode. It accepts only failed planning rejections with no file effects. It preserves the task, original plan/step evidence, settlement receipts, source deduplication, and consumed retry budget. - Stop on a replan rejection and report the blocker. Never use
transfer.history.delete, ordinary redo, a new non-previewtransfer.file, target cleanup, or evidence deletion to bypass a durable task's checks. Music and tasks with file-operation evidence require manual recovery. - Only records explicitly marked
legacymay calltransfer.history.deletewithout deleting source/target files, then continue withtransfer.fileafter the response confirms history deletion. Preserve verified identity, original storage/mode/destination, season/episode, and music entity fields. A verified complete album sharing one directory may be retried once as an album; an artist is never a transfer target. - Report verified corrections, accepted/queued replans, confirmed transfer successes, and remaining blockers accurately. A queued replan is not a completed transfer. Never reset or remove failure/retry evidence.
Comments
Markdown supported