{"version":"2.1.228","anchor":"expected-storage-write-failures-stop-showing-up-as-errors","canonical_anchor":"expected-storage-write-failures-stop-showing-up-as-errors","heading":"Expected storage write failures stop showing up as errors","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/expected-storage-write-failures-stop-showing-up-as-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Expected storage write failures stop showing up as errors\n\nOrdinary permission or path write failures no longer surface as error reports.\n\n**What**\n\nFailed writes to the session metadata cache caused by permissions, the environment, a missing file or an over-long path are now logged quietly rather than raised as error reports. Other write failures still report.\n\n**Details**\n\n- Treated as benign: failure classes \"permission\" and \"environment\", and codes \"UnexpectedAbsent\", \"ENOENT\" and \"ENAMETOOLONG\".\n\n**Evidence**\n\n`ENAMETOOLONG`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}