{"version":"2.1.228","anchor":"cross-session-inbox-startup-failures-record-why-they-failed","canonical_anchor":"cross-session-inbox-startup-failures-record-why-they-failed","heading":"Cross-session inbox startup failures record why they failed","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/cross-session-inbox-startup-failures-record-why-they-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Cross-session inbox startup failures record why they failed\n\nInbox startup now names whether binding or key publishing failed, and flags degraded starts.\n\n**What**\n\nStartup telemetry for the cross-session inbox now names the cause, either failing to bind the socket or failing to publish the key, rather than attributing every failure generically. A start that succeeds but is degraded is now reported as degraded instead of success.\n\n**Evidence**\n\n`getUdsStartFailureCause`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}