> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/troubleshooting/how-to-deal-with-error-s.md).

# How to deal with error(s)

On this page, we will explain how to deal with errors that occurred for any reason, without losing your uploaded/edited files.

Sometimes and for different reasons (connectivity problems, throttling..) the upload process could be interrupted and failed, this will give an error for each file and the files will be kept in Cache Folder:

```
%localappdata%\konnekt\cache
```

{% hint style="danger" %}
When error(s) occurs, files will remain in Cache folder until you deal with them.
{% endhint %}

The error(s) will be shown in KONNEKT Explorer window under **Errors**

![](https://2727108687-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8zLVuKYctMIUr68_fs%2F-MfWgsWo6RGwtB0NOxsv%2F-MfWjMwm-reQrf-t_iCZ%2F2021-07-26%2009_18_11-192.168.2.50%20-%20Remote%20Desktop%20Connection.png?alt=media\&token=c3bca764-b261-4074-b4bf-7a7aa73261c7)

By right mouse click on an error three options:

* **Retry failed upload:** this will retry the upload process again. If it success the error will automatically disappear
* **Export file to download folder:** this will export the file to your user download folder and delete the error automatically
* **Discard your changes:** this option will ignore the error without saving the file

![](https://2727108687-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8zLVuKYctMIUr68_fs%2F-MfWgsWo6RGwtB0NOxsv%2F-MfWlF7vCN75Ne6h34uw%2F2021-07-26%2009_19_56-192.168.2.50%20-%20Remote%20Desktop%20Connection.png?alt=media\&token=dadea302-4018-44db-ba33-43526805aa05)

### Deleting all Errors together

{% hint style="info" %}
This feature is applicable to version 2.0 and above
{% endhint %}

In some cases, you want to ignore all errors together (e.g. to free the Cache folder space), you can do it by right click on KONNEKT Icon in Explorer window and **Close file errors**

![](https://2727108687-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8zLVuKYctMIUr68_fs%2F-MfWgsWo6RGwtB0NOxsv%2F-MfWlrszF1ZVoci8b-Gj%2F2021-07-26%2009_18_43-192.168.2.50%20-%20Remote%20Desktop%20Connection.png?alt=media\&token=17146d14-d329-46b4-b0c9-01086b2e7364)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konnekt.io/troubleshooting/how-to-deal-with-error-s.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.