{"version":"2.1.248","anchor":"workers-retry-reading-session-auth-headers-at-startup","canonical_anchor":"workers-retry-reading-session-auth-headers-at-startup","heading":"Workers retry reading session auth headers at startup","tier":"internal","area":"Background Work","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/workers-retry-reading-session-auth-headers-at-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Workers retry reading session auth headers at startup\n\nA worker starting before its auth headers arrive now retries instead of dying.\n\n**What**\n\nA 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.\n\n**Details**\n\n- Each attempt logs `[remote-io] no auth headers, re-reading in ${...}ms`.\n- Success reports `cli_worker_lifecycle_init_auth_retried` at info level; running out of attempts reports `cli_worker_lifecycle_init_auth_retry_exhausted` at error level with the attempt count and diagnostics. Both event names are new in this build.\n\n**Evidence**\n\n`cli_worker_lifecycle_init_auth_retry_exhausted`, `cli_worker_lifecycle_init_auth_retried`, `[remote-io] no auth headers, re-reading in `\n\n- Area: Background Work\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}