You'll notice
Useful2 Signal1
Background state reads retry on transient errors instead of failing immediately.
What's wrong with this entry?
Anonymous. No account, no email.
What
Reads of background state now retry on a delay schedule while the error looks transient, so a momentarily unavailable read no longer surfaces as a failure.
Details
- Retried when the error is
Unavailable, orFailedbut outside a known set of permanent failure classes. - A read that succeeded only after retries reports
tengu_bg_state_read_recoveredwith the number of attempts; a clean first read is noted separately.
Evidence
tengu_bg_state_read_recovered
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.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task