{"version":"2.1.247","anchor":"renaming-a-session-warns-when-other-sessions-may-keep-the-ol","canonical_anchor":"renaming-a-session-warns-when-other-sessions-may-keep-the-ol","heading":"Renaming a session warns when other sessions may keep the old name","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/renaming-a-session-warns-when-other-sessions-may-keep-the-ol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Renaming a session warns when other sessions may keep the old name\n\nRenaming a session now warns you when the new name didn't reach other running sessions, pointing at --debug.\n\n**What**\n\nA rename that applied locally but failed to reach the shared record of running sessions now says so, and points you at `--debug` for the cause. It used to fail silently apart from an unrelated line about a PID file.\n\n**Details**\n\n- The rename result appends the caveat only when the shared record was not updated.\n- Also fixes a case where the confirmation printed the internal result object instead of the new name.\n\n**Evidence**\n\n`Other sessions may still show the old name: the session registry could not be updated (run with --debug for the cause)`, `applied locally but the session registry record was not updated`\n\n- Area: Sessions\n- Names: `--debug`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}