{"version":"2.1.265","anchor":"dir-sync-between-tools-publish-telemetry-now-tracks-how-long","canonical_anchor":"dir-sync-between-tools-publish-telemetry-now-tracks-how-long","heading":"dir-sync between-tools publish telemetry now tracks how long the sync was held","tier":"internal","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/dir-sync-between-tools-publish-telemetry-now-tracks-how-long","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### dir-sync between-tools publish telemetry now tracks how long the sync was held\n\nDirectory-sync publish telemetry now tracks how long a sync was held before sending\n\n**What**\n\nThe directory-sync 'between tools' publish logic was rewritten to start a due-check and await a snapshot-taken signal, and now reports a new `held_ms` field, alongside the existing `outcome` and `duration_ms`, in the `tengu_dir_sync_between_tools_publish` telemetry event.\n\n**Why**\n\n`held_ms` shows how long a sync was held before being published, giving a clearer picture of sync timing in the directory-sync system beyond just how long the operation itself took.\n\n- Area: Cloud Sync\n- Names: `held_ms`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}