{"version":"2.1.248","anchor":"reused-session-id-exits-with-an-identifiable-error-code","canonical_anchor":"reused-session-id-exits-with-an-identifiable-error-code","heading":"Reused session ID exits with an identifiable error code","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/reused-session-id-exits-with-an-identifiable-error-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Reused session ID exits with an identifiable error code\n\nReusing a session ID now exits with a machine-readable session_in_use code for SDK callers.\n\n**What**\n\nStarting with a session ID that is already in use now exits with the machine-readable code `session_in_use` alongside the message, so SDK and wrapper callers can tell this apart from other startup failures. The message you see is unchanged.\n\n**Evidence**\n\n`session_in_use`\n\n- Area: SDK\n- Names: `session_in_use`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}