# Log

Log contains the results of operations that are not directly related to the txt file, more to the application itself and its interaction with your operating system. The log lets you know whether the actions like opening, reloading or saving song went fine or whether there were some issues.

<figure><img src="/files/tb6LH4jtnphOxTWc0JeI" alt=""><figcaption></figcaption></figure>

Here is an example of logs that would appear if you tried to load an invalid audio file:

![](/files/ncpIQ2FrHUHbGMMznVSq)

## Log types

1. Success - marked with green check mark - mean that the operation completed successfully.\
   ![](/files/erwr1hqaPvhDg3d8Zt9s)
2. Warning - marked with yellow exclamation mark - mean that something unexpected was encountered but it may not necessarily cause the operation to fail.\
   ![](/files/VNtvjeuZIvWjUHqcUiGM)
3. Error - marked with red cross mark - mean that the operation failed.<br>

   <div align="left"><figure><img src="/files/voZrJnpv3r0TgATISUss" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
If you see a warning or an error log make sure to check what happened
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://karedi.gitbook.io/karedi/user-interface/lower-components/log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.