{"version":"2.1.250","anchor":"failed-live-watch-startups-are-treated-as-temporary-outages-","canonical_anchor":"failed-live-watch-startups-are-treated-as-temporary-outages-","heading":"Failed live-watch startups are treated as temporary outages and retried on the slow schedule","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250\/e\/failed-live-watch-startups-are-treated-as-temporary-outages-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250","markdown":"### Failed live-watch startups are treated as temporary outages and retried on the slow schedule\n\nLive artifact watches that fail to start from a server hiccup now retry on the patient schedule instead of burning attempts.\n\n**What**\n\nWhen a live artifact watch fails to start, Claude Code now decides whether the failure looks like a transient server problem rather than a permanent one, and routes it to the slow stall-style retry instead of the fast consecutive-failure backoff. A failure counts as a temporary outage if the server replied with a retryable status, or if the request produced no reply at all and hung for at least 10 seconds. Neither of these markers existed on this error path in 2.1.248.\n\n**Details**\n\n- The retryable-status test returns true for HTTP status 500 or above, 429 and 408; such a status attaches an `unavailable` marker to the startup response.\n- A startup error code of `boot_request_error` attaches a `noAnswer` marker, meaning the request errored out with no reply.\n- The startup builder records the time just before the request is issued, so a hung startup can be measured; a `noAnswer` result plus elapsed time of at least `stallThresholdMs`, the reconnect timing default compiled at 10000 ms, counts as unavailable.\n- The failure helper gained `unavailable` and `httpStatus` options and passes a `stalled` flag plus the HTTP status into the reconnect scheduler.\n- All of this sits inside the live-watch feature, which is off unless the `tengu_slate_lantern` flag is switched on for your account.\n\n**Evidence**\n\n`boot_request_error`, `...(i.errorCode === \"boot_request_error\" && { noAnswer: !0 }),`\n\n- Flag `tengu_slate_lantern`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.250; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}