{"version":"2.1.248","anchor":"background-sessions-report-a-taken-session-id-as-a-distinct-","canonical_anchor":"background-sessions-report-a-taken-session-id-as-a-distinct-","heading":"Background sessions report a taken session id as a distinct crash","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/background-sessions-report-a-taken-session-id-as-a-distinct-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Background sessions report a taken session id as a distinct crash\n\nBackground sessions that hit an already-claimed session id now fail with a clear dimmed notice.\n\n**What**\n\nIf a background session starts with an id another session already claims, it now ends on its own path: the session is marked `crashed`, a dimmed notice goes to the output stream, and a dedicated event is recorded with the attempt number, how it was launched and the launch mode. Previously this fell into the generic crash and exit handling.\n\n**Details**\n\n- Event name `tengu_bg_session_id_taken`, with `attempt`, `via` and `launch_mode` fields.\n- Unconditional on this code path; no flag.\n\n**Evidence**\n\n`tengu_bg_session_id_taken`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}