{"version":"2.1.248","anchor":"messaging-startup-warning-now-names-the-real-cause","canonical_anchor":"messaging-startup-warning-now-names-the-real-cause","heading":"Messaging startup warning now names the real cause","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/messaging-startup-warning-now-names-the-real-cause","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Messaging startup warning now names the real cause\n\nCross-session messaging startup warnings now name the actual cause instead of always blaming sockets.\n\n**What**\n\nWhen cross-session messaging fails to start, the warning used to always blame the socket directory setup. It now reports the specific cause: a refused socket path, a bind failure, a failure to publish this session's peer key, or a problem after binding. The old text remains as the fallback when the cause is unknown.\n\n**Details**\n\n- A companion helper records the degraded cause and declines to overwrite an existing one when the key publish failed after the primary directory was already refused.\n\n**Evidence**\n\n`its peer key could not be published`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}