{"version":"2.1.229","anchor":"overlong-filenames-are-no-longer-counted-as-expected-failure","canonical_anchor":"overlong-filenames-are-no-longer-counted-as-expected-failure","heading":"Overlong filenames are no longer counted as expected failures","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/overlong-filenames-are-no-longer-counted-as-expected-failure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Overlong filenames are no longer counted as expected failures\n\nOverly long file paths now count as real file-tracking failures instead of being quietly ignored.\n\n**What**\n\nThe 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.\n\n**Evidence**\n\n`e.telemetryCode === \"UnexpectedAbsent\"`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}