> 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.md).
# Errors and Failures
Movebot attempts to remedy all failures automatically, but there are some failure types that will require manual intervention and we cannot transfer the data across.
There are two main types of failures:
* Fatal Failures
* File or Folder Failures
Fatal failures occur when we cannot proceed with any transfers in a migration job and file or folder failures occur when there was an issue transferring or scanning a file or folder discovered under a transfer mapping (job).
### Viewing Errors
Errors can be found on an individual transfer mapping basis under **Error Tracker.**
### Failure Severities
Errors and failures in Movebot are categorized by severity as described below.
| Severity Rating | Example | Description |
| --------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Critical | Folder / Files failed to scan | Critical errors are generally very bad. These include an outright failure to scan a directory, which can lead to dataloss. |
| High | Could not create file x.txt | High severity errors are generally isolated to a single object. It is recommended that you address them on an individual basis. |
| Medium | File y.txt was ignored | Medium severity errors can normally be ignored, but should be noted as they can show incorrect configuration. |
| Low Severity | File !blah.txt was renamed to blah.txt | Low severity warnings are informational. |
### Error Resolution
Fixing errors generally comes down to two approaches:
* Adjustments in configuration or a manual transfer of the object
* Running a Delta
If the root cause is not obvious and it cannot be fixed through configuration, then attempt to run a Delta. If running a Delta does not fix the issue, then reach out to support at .
---
# 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.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.