Add watchdog and recovery behavior for stale imports #12

Open
opened 2026-07-29 12:25:21 +02:00 by daniels · 0 comments
Owner

Problem

Tdarr has operational resilience for stuck/limbo work. Importarr needs equivalent recovery for interrupted copies, stale queue items, and failed retries.

Proposed change

Implement watchdog/recovery behavior for stale import work.

Scope

  • Detect stale .partial files and decide whether to retry, clean, or mark failed.
  • Timeout stuck import jobs with a clear reason.
  • Retry policy with backoff and max attempts.
  • Health detail for stale queue/import conditions.
  • Optional systemd timer or worker heartbeat integration.

Acceptance criteria

  • Interrupted imports do not silently block future imports.
  • Stale jobs become visible in queue/health output.
  • Retry attempts and final failure are persisted in history.
  • Recovery behavior is documented and tested.
## Problem Tdarr has operational resilience for stuck/limbo work. Importarr needs equivalent recovery for interrupted copies, stale queue items, and failed retries. ## Proposed change Implement watchdog/recovery behavior for stale import work. ## Scope - Detect stale `.partial` files and decide whether to retry, clean, or mark failed. - Timeout stuck import jobs with a clear reason. - Retry policy with backoff and max attempts. - Health detail for stale queue/import conditions. - Optional systemd timer or worker heartbeat integration. ## Acceptance criteria - Interrupted imports do not silently block future imports. - Stale jobs become visible in queue/health output. - Retry attempts and final failure are persisted in history. - Recovery behavior is documented and tested.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: daniels/importarr#12