{"version":"2.1.277","anchor":"new-standing-lightweight-status-message-in-cloud-dir-sync","canonical_anchor":"new-standing-lightweight-status-message-in-cloud-dir-sync","heading":"Cloud file sync gains a lightweight 'standing' status message","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-standing-lightweight-status-message-in-cloud-dir-sync","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Cloud file sync gains a lightweight 'standing' status message\n\nThe cloud\/local file-sync protocol has a new lightweight 'standing' status distinct from a full sync report\n\n**What**\n\nThe git-based cloud\/local file-sync protocol gained a new, lightweight journal message kind called `standing`, decoded by a new function separate from the full worker note\/report. When a `standing` message is present, the client updates its local record from it and returns a new outcome code, `peer_standing`, instead of the usual outcomes like `nothing_new` or `applied`. This new `peer_standing` value was also added to the retry-outcome switch and related status enum, alongside existing states such as `no_journal`, `yielded`, `upload_only`, and `refused`.\n\n**Why**\n\nThis gives the sync protocol a cheap way to report a peer's status without sending a full sync report, which should make routine status checks lighter weight.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}