Count a timed-out resume as an attempt, it may have launched

2026-08-18 21:20:45 +02:00
parent 5a5dc94ae8
commit 673632ff21
2 changed files with 8 additions and 1 deletions
@@ -91,7 +91,9 @@ endless chain of blocked jobs:
 again it is a *new* session id and qualifies on its own, so an outage spanning
 several reset windows still gets retried. What the cap prevents is one
 conversation being resumed into several concurrent copies. A resume that fails
-to launch at all records no attempt and is retried on the next tick.
+to launch at all records no attempt and is retried on the next tick; one that
+times out records an attempt, because the launch may have registered after the
+watchdog stopped waiting for it.

 `--max-per-day` is the one guard that cannot be derived from anything else. A
 usage-limit block is self-pacing, because the stated reset time is respected —