Under the hood
Useful2 Signal2
A worker starting before its auth headers arrive now retries instead of dying.
What's wrong with this entry?
Anonymous. No account, no email.
What
A worker that starts before its session authentication headers are available now re-reads them on a fixed delay schedule rather than failing outright, so a slow handoff no longer kills the worker.
Details
- Each attempt logs
[remote-io] no auth headers, re-reading in ${...}ms. - Success reports
cli_worker_lifecycle_init_auth_retriedat info level; running out of attempts reportscli_worker_lifecycle_init_auth_retry_exhaustedat error level with the attempt count and diagnostics. Both event names are new in this build.
Evidence
cli_worker_lifecycle_init_auth_retry_exhausted, cli_worker_lifecycle_init_auth_retried, [remote-io] no auth headers, re-reading in
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