{"version":"2.1.242","anchor":"messages-to-a-cloud-session-wait-until-it-has-your-local-fil","canonical_anchor":"messages-to-a-cloud-session-wait-until-it-has-your-local-fil","heading":"Messages to a cloud session wait until it has your local files","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/messages-to-a-cloud-session-wait-until-it-has-your-local-fil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Messages to a cloud session wait until it has your local files\n\nMessages to a cloud session wait until your uploaded files have actually landed there.\n\n**What**\n\nWhen directory sync is on, a message you send to a cloud session is held until the session confirms it applied the files uploaded from your machine, polled with exponential backoff up to a cap. If that never happens you get a plain-language explanation instead of silence.\n\n**Details**\n\n- Timeout produces its own message; a partial apply names how many files could not be fetched.\n- Each container-side refusal maps to a sentence, covering a bundle timeout, the uploaded state not being a descendant of what the session has, a dirty working tree, a refused checkout and a git timeout.\n- Two new telemetry events record the wait and each held send.\n- Only sessions with directory sync active reach this path.\n\n**Evidence**\n\n`tengu_dir_sync_seed_gate_send`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}