> 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/troubleshooting/errors-and-failures/common-errors/error-file-not-found.md).

# Error: file-not-found

|                |                |
| -------------- | -------------- |
| Error Type     | file-not-found |
| Relevant Store | All            |

## Description

File Not Found errors are caused by us not being able to find and download the file in the store. 

{% hint style="info" %}
During the scan stage of a migration (the first step), Movebot builds a map of all files to be transferred. If files change after the scan, this can cause issues.
{% endhint %}

## Common Root Causes

* The file has been moved
* The file is not accessible due to permissions
* The filename has changed

## Quick Fixes

* Check that the connected account has appropriate permissions to download the affected files.

After attempting a fix, rerun failures or run a new delta migration to see if the error is resolved. 


---

# 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/troubleshooting/errors-and-failures/common-errors/error-file-not-found.md?ask=<question>&goal=<endgoal>
```

`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.