{"version":"2.1.227","anchor":"resuming-a-conversation-explains-symlinked-or-unreadable-tra","canonical_anchor":"resuming-a-conversation-explains-symlinked-or-unreadable-tra","heading":"Resuming a conversation explains symlinked or unreadable transcripts","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/resuming-a-conversation-explains-symlinked-or-unreadable-tra","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Resuming a conversation explains symlinked or unreadable transcripts\n\nResuming explains when a transcript is a symlink or couldn't be read.\n\n**What**\n\nTwo new refusals when opening a stored conversation. A transcript file that is a symbolic link or not a regular file is refused, with advice to resume from the directory holding the real file. A transcript that could not be read at that moment now says so rather than failing generically.\n\n**Evidence**\n\n`This conversation's file is a symbolic link or not a regular file, so it can't be opened from here`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}