{"version":"2.1.229","anchor":"session-load-failures-now-explain-themselves","canonical_anchor":"session-load-failures-now-explain-themselves","heading":"Session load failures now explain themselves","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/session-load-failures-now-explain-themselves","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Session load failures now explain themselves\n\nWhen a session transcript won't load, you're told exactly why in plain words.\n\n**What**\n\nWhen a session transcript cannot be read, the error says why in plain words: the file is a symbolic link, something other than a regular file is in its place, it exceeds the size limits, or it changed while being read, in which case you are told to run the command again.\n\n**Details**\n\n- Replaces raw filesystem error codes in the session load path.\n- Symlinked transcripts are reported as unsupported rather than silently followed.\n\n**Evidence**\n\n`this session's transcript is a symbolic link, which session storage does not read through.`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}