You'll notice
Useful2 Signal1
Sync-unreachable warnings now word themselves differently for background and foreground passes.
What's wrong with this entry?
Anonymous. No account, no email.
What
When 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 — 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.
Details
- The wording is chosen from the pass's trigger type, so the reassuring version only appears for passes you did not initiate.
- Neither version changes what sync actually does; only the message differs.
Evidence
sync has not stopped
Strings lifted out of the shipped bundle, so the claim above can be checked against them.