The dispatched-work reminder now follows interval changes and asks Claude for a time estimate.
What's wrong with this entry?
The reminder that fires while dispatched work is still running now checks the current interval on each tick and re-arms itself if it has changed, instead of quietly running on the old schedule. Its wording also changed: it is summarised as "Worker check-in: dispatched work still running" and now asks the model to tell you how long it expects the work to take, rather than to post a status.
- Re-arming carries over the same task registry and known worker set.
- A new helper registers an additional worker into a check-in that is already armed, instead of starting a second one.
Worker check-in: dispatched work still running
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Background job state and roster writes can route through the v5 storage backend
Both mention background
-
v2.1.223
Telemetry for transient background-job state read failures
Both mention background
-
v2.1.223
Roster orphan adoption reports itself
Both mention background