You'll notice
Useful3 Signal2
A background worker that never starts is named as a start failure instead of hanging until timeout.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a background worker fails to launch, the failure is now recorded instead of leaving a gap. The sync journal that a cloud session writes for the laptop side can mark itself halted with a reason and the line involved, and a placeholder transcript record is produced in its place, so the laptop names the worker that never came up rather than waiting for a timeout.
Details
- the placeholder transcript record is marked halted with reason
start_failedand attributed to the worker side - the journal halt entry carries both the reason and the line involved
- a decoder for the start-failed case lets the laptop read these entries and surface them
Evidence
decodeWorkerStartFailed, start_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.