Repository navigation
Nightbell 3.17.0
Failures before an alert are now confirmed 30 seconds apart, inside the same background run that saw the first one, instead of one scheduled check apart. A threshold of three used to mean half an hour of a site being down before the phone said anything. Now it is about a minute.
| Failures before alerting | Before, at best | Now |
|---|---|---|
| 2 | 15 min | 30 s |
| 3 | 30 min | 1 min |
| 5 | 1 h | 2 min |
| 10 | 2 h 15 min | 4 min 30 s |
Where it is: Retry right away, under Escalation next to Failures before alerting, both in Settings, Alerts and in a monitor's own alert settings. It only shows when the threshold is above one, because a single failure already alerts. It is on by default, including for monitors set up before this version.
What a failing card says: "1 of 3 failures before it alerts", so a red card that has not paged you yet tells you why.
When it does not retry: the phone is offline, monitoring is paused, the monitor is muted or alerts are switched off, since nothing would be posted at the end of it. A check that failed because the phone lost signal is not counted as a failure. GitHub repository monitors stay on their schedule, because they share a rate limit with everything else on the token.
When the phone is asleep: Android decides, not Nightbell. Measured on Android 14 with the phone forced into deep Doze: with battery optimisation on, Android stops the background run the moment the phone goes idle and cuts its network, so the remaining retries wait for the next scheduled check, which is what happened before this release. With Nightbell exempt, the same run kept retrying 30 seconds apart through deep idle and paged on time. The exemption is one button under Settings, Checks, Checker health. In strict mode the service loop runs the retries itself.
Reported in #20.