Three new remote-bridge switches appear, covering a retry after a rejected token refresh and two unread ones.
tengu_dazzling_garden Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.238: off
tengu_bridge_host_declined_end Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.238: off
tengu_bridge_signed_out_neutral Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.238: off
Read once, for one account on one subscription tier, against v2.1.238. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Three new remote-bridge feature checks appear, all defaulting to on when the server says nothing. tengu_dazzling_garden guards a second OAuth recovery attempt after a forced token refresh is rejected. tengu_bridge_host_declined_end and tengu_bridge_signed_out_neutral are present in the build, but what reads them is not visible from the flag definitions.
tengu_dazzling_garden
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