{"version":"2.1.247","anchor":"failed-cross-session-inbox-bind-records-why-it-failed","canonical_anchor":"failed-cross-session-inbox-bind-records-why-it-failed","heading":"Failed cross-session inbox bind records why it failed","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/failed-cross-session-inbox-bind-records-why-it-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Failed cross-session inbox bind records why it failed\n\nWhen the cross-session inbox fails to open, diagnostics now say why.\n\n**What**\n\nWhen the socket that receives messages from other sessions fails to bind late in startup, the recorded reason is now the actual cause rather than a flat \"bind failed\", making these failures distinguishable in diagnostics.\n\n**Evidence**\n\n`[uds-messaging] Late bind refused: `\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}