Skip to content

Surface failed/stuck episodes and library health #13

Description

@frarredondo

Summary

Failed or never-started episodes are easy to miss in a large sync, and empty feeds are not obvious.

Motivation / evidence

Example: the-programming-podcast is registered but had 0 transcripts while other feeds filled up. Overnight syncs need a clear “what still needs attention?” view.

Proposal

Add a health/status path, either via richer show/feeds or a dedicated command:

podtx doctor
# or
podtx show --failed

Report failed/stuck/pending episodes, empty feeds, and basic data-dir sanity checks.

Out of scope

Automatic retry policies beyond what’s already in sync (can be a follow-up).

Acceptance criteria

  • Users can list episodes that need attention without digging through logs
  • Empty/unhealthy feeds are visible
  • Docs / --help updated

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions