{"version":"2.1.269","anchor":"skills-sync-resync-now-records-why-it-fired-and-how-late-it","canonical_anchor":"skills-sync-resync-now-records-why-it-fired-and-how-late-it","heading":"Skills sync resync now records why it fired and how late it was","tier":"internal","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/skills-sync-resync-now-records-why-it-fired-and-how-late-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Skills sync resync now records why it fired and how late it was\n\nSkills-sync resync ticks now record why they fired and report when one is skipped after the machine slept too long.\n\n**What**\n\nThe periodic scheduler that resyncs skills (packaged instruction sets Claude Code can load) now labels each resync tick with a trigger reason, either `resync` (a regular scheduled run) or `wake_settle` (following the machine waking from sleep). It also sends a new telemetry event, `tengu_skills_sync_resync_skipped`, when a resync tick is skipped because the machine had been asleep too long.\n\n**Why**\n\nThis makes it possible to tell, from telemetry, whether skills stayed in sync correctly across sleep\/wake cycles, and to see when a resync was skipped rather than assuming it always ran.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}