{"version":"2.1.273","anchor":"new-telemetry-event-for-publish-rejected-due-to-an-unrecogni","canonical_anchor":"new-telemetry-event-for-publish-rejected-due-to-an-unrecogni","heading":"New telemetry event for publish rejected due to an unrecognized\/not-served file path","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-telemetry-event-for-publish-rejected-due-to-an-unrecogni","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New telemetry event for publish rejected due to an unrecognized\/not-served file path\n\nA new telemetry event reports the specific file path when a publish is rejected for an unrecognized path\n\n**What**\n\nWhen publishing files fails because a file's path isn't recognized as served (an internal check returns `notServedPath`), Claude Code now fires a `files_invalid` telemetry event carrying the specific rejected path, in addition to throwing the existing error.\n\n**Why**\n\nThis gives more detail for diagnosing publish failures caused by unrecognized file paths, since the exact path involved is now captured rather than just the fact that an error occurred.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}