{"version":"2.1.281","anchor":"directory-sync-worker-can-replay-its-own-recorded-links-and","canonical_anchor":"directory-sync-worker-can-replay-its-own-recorded-links-and","heading":"Directory sync worker can replay its own recorded links and caps them","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/directory-sync-worker-can-replay-its-own-recorded-links-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Directory sync worker can replay its own recorded links and caps them\n\nThe cloud directory-sync worker can reuse links it recorded itself and now stops the link store at size limits\n\n**Unclear.** The finding does not say what these links are or what a reader would notice when the cap is reached.\n\n**What**\n\nWhen the cloud directory-sync worker (the background process that copies your project into a cloud session) starts from an empty state, it now uses links it recorded itself as well as those from your machine. The link store now stops when it hits a limit on:\n\n- rows\n\n- bytes\n\n- an overall cap\n\nLinks marked with a `via` are no longer passed on. Two timing settings, `beforeTurnCapMs` and `pullPointRetryDelaysMs`, were removed.\n\n**Why**\n\nIn practice the worker can rebuild more of its state on a fresh start, and the link store can no longer grow without limit.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}