Not switched on
Useful2 Signal2
Team config files gained an alternate storage path with retry logic that isn't active by default.
The teammate team-file reader and mutator have a storage-backend path with retries; the file path still runs without a backend.
What's wrong with this entry?
Anonymous. No account, no email.
What
The teammate team-file reader and its locked mutator gained a storage-backend path that reads with readText and writes with ifMatch on the version observed at read time.
Details
- retries up to 5 times on
PreconditionFailedand onUnavailablewith lock telemetry codes - errors are formatted with code, failureClass and telemetryCode
- best-effort writes downgrade recognised transient failure classes to a log line instead of throwing
Evidence
Team file write failed (storage v5)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.