mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-19 08:12:52 +00:00
fix(notifications): rest a channel that had nobody to send to
A send with no browser subscribed, no iPhone paired or a transport the operator has not set up no longer counts as a failure, but nothing else replaced it. The mood reminder and the daily briefing retry every minute until delivered, so such a channel wrote a skipped row each minute, for good; the dispatch still counted as an attempt, so the watchdog and status alerts took it as announced; and the status screen said "active" with no hint why nothing arrived. The channel now rests for an hour after such a send, with the reason on its status, and the send does not count as an attempt. Subscribing a browser or pairing an iPhone ends the rest at once.
This commit is contained in:
1 parent
95e2ba5477
commit
4ff3e4e1b7
7 files changed
+97
-7
No files matched your search
@@ -105,7 +105,7 @@ const channelDeliveryStatus = z
|
||||
state: z
|
||||
.enum(["active", "auto_disabled", "manually_disabled", "sending_paused"])
|
||||
.describe(
|
||||
"Server-derived. `auto_disabled` — the dispatcher turned it off after repeated hard rejects (`disabledReason` says why). `manually_disabled` — the user turned it off. `sending_paused` — still enabled but inside a retry cooldown until `nextRetryAt`. `active` — enabled and sending.",
|
||||
"Server-derived. `auto_disabled` — the dispatcher turned it off after repeated hard rejects (`disabledReason` says why). `manually_disabled` — the user turned it off. `sending_paused` — still enabled but inside a retry cooldown until `nextRetryAt`, after a transient failure or after a send that had nobody to go to (no browser subscribed, no iPhone paired, a transport the operator has not set up; `lastFailureReason` names it, `consecutiveFailures` is not raised). `active` — enabled and sending.",
|
||||
),
|
||||
disabledReason: z
|
||||
.string()
|
||||
|
||||
Reference in new issue
Block a user