You'll notice
Useful3 Signal1
Background jobs with clashing names get a numbered suffix so you can tell them apart.
What's wrong with this entry?
Anonymous. No account, no email.
What
Before a background session starts, its name is checked against the names of existing jobs and, if it clashes, is given a suffix like (2). Repeat clashes read the existing number back out and increment it.
Details
- The seed records that the name came from a collision rather than being chosen directly.
- Renaming is best effort: if the list of existing jobs cannot be read, the original name is used as is.
Evidence
nameSource: "collision"
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