{"version":"2.1.238","anchor":"remote-inbox-fetching-is-instrumented-but-has-no-working-pat","canonical_anchor":"remote-inbox-fetching-is-instrumented-but-has-no-working-pat","heading":"Remote inbox fetching is instrumented but has no working path","tier":"soon","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/remote-inbox-fetching-is-instrumented-but-has-no-working-pat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Remote inbox fetching is instrumented but has no working path\n\nFetching a message from a remote inbox is measured in detail but always refuses.\n\n**What**\n\nThe function that would fetch a message from a remote inbox now records every outcome to a `bridge_inbox_fetch` telemetry event and gained a `no_bridge` reason. It still ends with an unconditional refusal, and no branch anywhere in the build actually fetches a message, so the capability is declared and measured but not implemented.\n\n**Details**\n\n- No flag, setting or environment variable enables a success path; the code for one is not present.\n\n**Evidence**\n\n`bridge_inbox_fetch`\n\n- Area: Remote Bridge\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}