{"version":"2.1.272","anchor":"new-background-runner-epochretry-constants-for-session-fail","canonical_anchor":"new-background-runner-epochretry-constants-for-session-fail","heading":"New background-runner epoch\/retry constants for session failure handling","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.272\/e\/new-background-runner-epochretry-constants-for-session-fail","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.272","markdown":"### New background-runner epoch\/retry constants for session failure handling\n\nNew retry timing and stale-session detection added to background session failure reporting\n\n**What**\n\nThe background runner's failure-reporting path, covering `runner:session` and `runner:stuck` logging, gained new timing constants (500ms, 1000ms, 2000ms, and 3000ms) and an abort helper. These are used when retrying a failed attempt to post a failure result, and to detect when another runner has already taken over a session, logged as a \"stale epoch\" rejection.\n\n**Why**\n\nThis makes background session failure handling more robust: retries are now timed explicitly, and a runner can tell when it's no longer the current owner of a session instead of continuing to report against it.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}