Fetching a message from a remote inbox is measured in detail but always refuses.
The inbox fetch records outcomes to telemetry and ends in an unconditional refusal, with no branch that actually fetches.
What's wrong with this entry?
The 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.
- No flag, setting or environment variable enables a success path; the code for one is not present.
bridge_inbox_fetch
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.222
Bridge recovery has a rebuild budget and richer failure telemetry
Both mention bridge
-
v2.1.224
Two new remote-config gates for bridge event forwarding
Both mention bridge
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge