{"version":"2.1.281","anchor":"cloud-file-sync-branch-message-when-git-was-busy","canonical_anchor":"cloud-file-sync-branch-message-when-git-was-busy","heading":"Cloud file sync: branch message when git was busy","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-branch-message-when-git-was-busy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file sync: branch message when git was busy\n\nCloud file sync now says when your branch has not caught up with Claude's latest commit because git was busy\n\n**What**\n\nSometimes cloud file sync cannot move your branch because git is busy in your checkout, the copy of the project on your machine. This is the `index_busy` case. After two or more tries, it now has its own message: \"Your branch has not moved to Claude's latest commit yet: git was busy in this checkout. It is tried again a few times over the next minutes; after that your next message carries on from what you have\".\n\n**Why**\n\nYou are told why your branch is behind and what happens next. The message makes clear that retries are limited, and that after them your next message works from what you have locally.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}