{"version":"2.1.251","anchor":"sync-unreachable-warning-now-reads-differently-for-backgroun","canonical_anchor":"sync-unreachable-warning-now-reads-differently-for-backgroun","heading":"Sync-unreachable warning now reads differently for background passes","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/sync-unreachable-warning-now-reads-differently-for-backgroun","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Sync-unreachable warning now reads differently for background passes\n\nSync-unreachable warnings now word themselves differently for background and foreground passes.\n\n**What**\n\nWhen file sync cannot reach the cloud session, the warning text depends on which kind of sync pass failed. A background pass says \"it keeps trying at each sync point \u2014 nothing is lost, and sync has not stopped\". A foreground send still says your message waits while sync tries a few more times, and that Esc cancels the message.\n\n**Details**\n\n- The wording is chosen from the pass's trigger type, so the reassuring version only appears for passes you did not initiate.\n- Neither version changes what sync actually does; only the message differs.\n\n**Evidence**\n\n`sync has not stopped`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}