> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/using-movebot/transfer-execution-and-cutover/failures-and-errors.md). # Failures and Errors ### Handling Failures with Confidence While Movebot is designed to be reliable, occasional failures can happen—especially when dealing with varying cloud platforms and environments. The good news? Most issues are easy to fix, and failures are **nothing to be afraid of**. We’re here to help you handle them with ease. *** ### First Step: Resume Job / Rerun Failures If you have a finished transfer with outstanding failures, your first action should be to **Resume Job / Rerun Failures**. This simply resets the status of any failed files and tries again. This action does not require a re-scan of the source data. To rerun failures: 1. Open your project and select any jobs that have failures. 2. Click **Launch Scan or Transfer**. 3. Select **Resume Job / Rerun Failures**. This often clears up transient or permission-based issues with minimal effort. *** ### Secondary Option: Start a Delta Migration If some failures persist—particularly with error types such as **unknown errors**, **file-not-found**, or **checksum-mismatch**—running a **Delta Migration** can be helpful. Delta migrations scan for and retry transferring files that have changed, or failed previously, without reprocessing files that have already migrated successfully. To start a delta migration: 1. Open the project and select any jobs that have failures. 2. Click **Launch Scan or Transfer**. 3. Select **Start Delta Migration**. This is a safe and efficient way to retry specific problem files without restarting the entire job. ### Investigating Persistent Failures Movebot displays detailed failure information in the **admin interface**, including the original error message returned from the cloud platform. This can help pinpoint the reason a file failed to transfer. ### Still Need Help? If the reason for failure remains unclear, we’re happy to assist. 📩 **Contact support at** \ Our team can review the issue and guide you to a solution. ***
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.movebot.io/using-movebot/transfer-execution-and-cutover/failures-and-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.