{"version":"2.1.260","anchor":"new-telemetry-event-for-failed-rewinds","canonical_anchor":"new-telemetry-event-for-failed-rewinds","heading":"New telemetry event for failed rewinds","tier":"internal","area":"File History","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-telemetry-event-for-failed-rewinds","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New telemetry event for failed rewinds\n\nA new telemetry event logs when a file-history rewind fails entirely.\n\nA new `tengu_file_history_rewind_failed` telemetry event is emitted, with `trackedFilesCount`, `filesFailedCount`, and `skippedLinksCount`, when a rewind fails because no files could be restored.\n\n- Area: File History\n- Names: `tengu_file_history_rewind_failed`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}