Under the hood
Useful2 Signal2
Overly long file paths now count as real file-tracking failures instead of being quietly ignored.
What's wrong with this entry?
Anonymous. No account, no email.
What
The classifier deciding whether a file-tracking failure is routine dropped the overlong-filename error code. Only permission and environment errors, missing files and unexpectedly absent entries are now treated as expected, so path-length failures show up as real ones.
Evidence
e.telemetryCode === "UnexpectedAbsent"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.