{"version":"2.1.281","anchor":"dir-sync-first-upload-interrupted-notices-and-silent-not-ar","canonical_anchor":"dir-sync-first-upload-interrupted-notices-and-silent-not-ar","heading":"Dir-sync: first-upload-interrupted notices and silent not-armed recording","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dir-sync-first-upload-interrupted-notices-and-silent-not-ar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dir-sync: first-upload-interrupted notices and silent not-armed recording\n\nDirectory sync now says when a folder's upload was cut short or never began, and records a quiet not-armed case\n\n**Unclear.** The finding does not say whether recording through `noteSilentlyNotArmed` shows you anything.\n\n**What**\n\nNew messages cover a folder upload that was interrupted or never started. One reads: \"The upload of this folder's files never began, so this cloud session starts empty and will not sync with this folder.\"\n\nOne case where sync is not armed (not set up to run) used to be dropped without any trace. It is now recorded through `noteSilentlyNotArmed`.\n\n**Why**\n\nYou are now told when a cloud session starts without your folder's files, instead of finding out later that nothing synced."}