Re-armed artifact watches could reuse an existing connection instead of starting over, but the flag is off.
Subscription reuse and renewal for artifact watches sits behind tengu_slate_lantern_ember, which falls back to false.
tengu_slate_lantern_ember Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.236: on
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When a live artifact watch is automatically re-armed, it can reuse a cached subscription token or renew it rather than starting a fresh subscription each time. This sits behind the gate tengu_slate_lantern_ember, which falls back to false in this build.
- The cached token's lifetime is clamped between 30 and 60 minutes.
- Reconnect backoff switches to a spread window when this mode is active.
- Reuse and renewal are reported in the subscribe telemetry as
token_reused,lease_remaining_minandtoken_renewed; failed renewals appear asrenew_miss_*.
restored_consent_not_editor
Strings lifted out of the shipped bundle, so the claim above can be checked against them.