Failures and Errors
Learn about how Movebot handles 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:
Open your project and select any jobs that have failures.
Click Launch Scan or Transfer.
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:
Open the project and select any jobs that have failures.
Click Launch Scan or Transfer.
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 support@movebot.io Our team can review the issue and guide you to a solution.
Last updated
Was this helpful?