{"version":"2.1.250","anchor":"giving-up-on-a-stalled-watch-is-spread-across-a-15-minute-wi","canonical_anchor":"giving-up-on-a-stalled-watch-is-spread-across-a-15-minute-wi","heading":"Giving up on a stalled watch is spread across a 15-minute window","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250\/e\/giving-up-on-a-stalled-watch-is-spread-across-a-15-minute-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250","markdown":"### Giving up on a stalled watch is spread across a 15-minute window\n\nStalled watches now give up somewhere between 30 and 45 minutes, not all at once.\n\n**What**\n\nA stalled watch used to be abandoned at exactly 30 minutes. Each stall run now picks its own deadline of 30 minutes plus a random amount up to 15 more, so sessions caught in one outage do not all give up together.\n\n**Details**\n\n- The new jitter constant is `stallOutJitterMs: 900000`.\n- The window deciding whether a fresh stall continues the previous run also widened, and now accounts for the long backoff band and twice the 15 second request timeout.\n\n**Evidence**\n\n`stallOutJitterMs: 900000,`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}