{"version":"2.1.228","anchor":"resuming-a-session-behind-a-symlink-explains-what-to-do","canonical_anchor":"resuming-a-session-behind-a-symlink-explains-what-to-do","heading":"Resuming a session behind a symlink explains what to do","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/resuming-a-session-behind-a-symlink-explains-what-to-do","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Resuming a session behind a symlink explains what to do\n\nIf a transcript is a symlink, resume now explains the problem instead of showing a raw error.\n\n**What**\n\nIf resuming a session fails because the transcript file is a symbolic link, you now get a specific explanation instead of the raw system error.\n\n**Details**\n\n- Triggered when the underlying error code is ELOOP.\n- The message says session storage does not read through the link, and tells you to put the original file back if you made the link yourself, or remove the link otherwise.\n\n**Evidence**\n\n`which session storage does not read through. If you made that link yourself, put the original file back in its place; otherwise remove the link.`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}