Push notifications for stale data and failing jobs (ntfy/webhook) #49
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add an optional
NOTIFY_WEBHOOK_URL(ntfy-compatible POST) and a daily check job in the existing background-jobs framework that fires on: no new usage rows in N days (configurable, default 35 — one missed monthly import), M consecutive failed jobs for a home, or a calculation stuck failed. Include home name and reason. No new infrastructure: reuse the jobs table, scheduling, and the fetch-timeout helper from #31.Rationale: the backend already computes staleness and job failure but surfaces them only inside the app. A homelab operator's real failure mode is not opening the app — imports quietly stop and weeks later the numbers are fiction.
Acceptance criteria
Relations: relates to #13 (shares the sync/job machinery), #31
(Audit finding F-30, 2026-07-16 — feature, ranked #5)