{"version":"2.1.280","anchor":"home-seed-dir-sync-standing-hold-flag-on-the-first-send","canonical_anchor":"home-seed-dir-sync-standing-hold-flag-on-the-first-send","heading":"Home-seed \/ dir-sync 'standing' hold flag on the first-send gate","tier":"internal","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/home-seed-dir-sync-standing-hold-flag-on-the-first-send","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Home-seed \/ dir-sync 'standing' hold flag on the first-send gate\n\nFile-sync's first-send gate gets a new 'standing' setting controlling whether a hold expires or persists\n\n**What**\n\nThe file-sync 'seed gate,' which can hold back the very first outbound send of a file until a release or withdrawal decision is made, now has a `standing` flag in its configuration. Previously a hold was always time-boxed, limited to one hold per fixed time window. With `standing` set, one implementation of the gate removes that time-box entirely, while a related implementation instead forces the hold to keep persisting rather than expiring on its own.\n\n**Why**\n\nThis changes whether a sync hold on a newly-created file clears itself automatically after a set time or stays in place until something explicitly releases it.\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}