{"version":"2.1.232","anchor":"resuming-with-an-unrecognisable-session-id-now-forks-instead","canonical_anchor":"resuming-with-an-unrecognisable-session-id-now-forks-instead","heading":"Resuming with an unrecognisable session id now forks instead of resuming","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/resuming-with-an-unrecognisable-session-id-now-forks-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Resuming with an unrecognisable session id now forks instead of resuming\n\nAn unparseable --resume session id now forks and replays instead of quietly resuming.\n\n**What**\n\nThe session id given by `--resume` or by the launch config is validated before use. A valid id resumes as before; a non-empty id that does not parse now takes the fork and replay path rather than silently resuming. v2.1.231 resumed on any non-empty id.\n\n**Details**\n\n- Accepted forms are a plain UUID, or a prefixed identifier matching `^[A-Za-z0-9][A-Za-z0-9_]*$` whose trailing `01`-prefixed base58 segment decodes to a 32-hex-digit UUID.\n\n**Evidence**\n\n`\/^[A-Za-z0-9][A-Za-z0-9_]*$\/.test(e)`\n\n- Area: Sessions\n- Names: `--resume`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}