{"version":"2.1.251","anchor":"directory-sync-tracks-its-journal-and-object-lanes-separatel","canonical_anchor":"directory-sync-tracks-its-journal-and-object-lanes-separatel","heading":"Directory sync tracks its journal and object lanes separately","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/directory-sync-tracks-its-journal-and-object-lanes-separatel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Directory sync tracks its journal and object lanes separately\n\nDirectory sync tracks two failure lanes separately so a stale journal is reported on its own.\n\n**What**\n\nThe background worker that syncs a directory over git no longer treats a failure as one general offline state. It now counts failures on its journal lane and its object lane independently, so a stale journal is logged and surfaced as its own condition, and it takes a new wait-before-proceeding duration that applies to whichever lane is down.\n\n**Details**\n\n- The offline signal is reported per lane, with the journal lane named specifically when it is the stale one, instead of a single shared counter covering both.\n- A configurable duration, internally `laneDownProceedMs`, sets how long the worker waits before proceeding while a lane is down.\n- Applies to cloud and self-hosted sessions that use directory sync.\n\n**Evidence**\n\n`dir_sync_git_worker_offline`, `laneDownProceedMs`\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}