{"version":"2.1.277","anchor":"filehistory-backup-restore-returns-structured-outcomes-inste","canonical_anchor":"filehistory-backup-restore-returns-structured-outcomes-inste","heading":"FileHistory backup restore returns structured outcomes instead of throwing","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/filehistory-backup-restore-returns-structured-outcomes-inste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### FileHistory backup restore returns structured outcomes instead of throwing\n\nFile-history backup restore now reports structured failure reasons instead of crashing\n\n**What**\n\nWhen Claude Code restores a backup file during a rewind or checkpoint, the restore step now returns a structured result describing what happened, instead of throwing an error. The result says whether the restore failed, was already present, or was migrated, and, on failure, at which stage it failed: a bad backup source, or a problem at the source, link, copy, or rename step.\n\nRename failures now log a clearer explanation of the likely cause, such as a scanner or sync tool still holding the newly written file, or a mount that allows creating files but not renaming them.\n\n**Why**\n\nThis makes backup-restore failures easier to diagnose instead of surfacing as a generic crash, and it explains real-world causes like antivirus scanners or cloud-sync tools interfering with file operations.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}