{"version":"2.1.248","anchor":"refused-socket-directory-now-says-which-path-component-was-r","canonical_anchor":"refused-socket-directory-now-says-which-path-component-was-r","heading":"Refused socket directory now says which path component was rejected","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/refused-socket-directory-now-says-which-path-component-was-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Refused socket directory now says which path component was rejected\n\nA refused messaging socket directory now names the exact path component rejected.\n\n**What**\n\nWhen the messaging sockets directory cannot be set up safely, the log line now names the specific path component that was refused, and the failure is recorded with a detail field alongside the existing `socket_dir_refused` cause. Cross-session messaging is still switched off for the session when this happens.\n\n**Evidence**\n\n`cross-session messaging is OFF for this session`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}