> For the complete documentation index, see [llms.txt](https://karedi.gitbook.io/karedi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://karedi.gitbook.io/karedi/user-interface/lower-components/problems-manager.md).

# Problems manager

How to check and solve issues with your songfile?

Your songfile is constantly being automatically analyzed by Karedi. Any issues are reported in the *Problems* tab which can be found below the [*main editor*](/karedi/user-interface/middle-components/main-editor.md)*.* By default problems tab is hidden and [*Log* ](/karedi/user-interface/lower-components/log.md)tab is visible. To switch to problems tab simply click on its caption.

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2F2pA0iaxmD5keHmIC3a6f%2Fimage.png?alt=media&amp;token=f8601082-2382-4849-84bd-e022158516dc" alt=""><figcaption></figcaption></figure>

## Problem types

Depending on the importance the found issues are divided into 2 categories:

* errors - problems of high importance - they will hinder the player's singing experience,
* warnings - problems of lower importance that should be fixed but they won't affect the user's experience that much.

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FxDho9kvWDRXKbe7Ar2Ab%2Fimage.png?alt=media&amp;token=75dd7291-e522-4e52-be86-9f60d7419df0" alt=""><figcaption></figcaption></figure>

If you click on the given category you can expand it and see the list of the problems that belong to it. If you hover the mouse on some problem you will see more details about it:

![](https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FNyWFm5gOi1jYL1rMM7eT%2Fimage.png?alt=media\&token=9f925090-8574-4f18-8c04-a5b50494ad10)

## Automatic fixes

For most of the problems you have an automatic fix available that you can apply. The automatic fix can be either safe or potentially risky.

If you right-click on some issue you will see the options to correct it:

&#x20;![](https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FAEZ0JqhDJEB5K6ChPlJ9%2Fimage.png?alt=media\&token=e581453b-73ea-49fe-83c1-6383b6a36ee2)

{% hint style="info" %}
You should use *Correct (invasive)* option if safe *Correct* option is unavailable
{% endhint %}

This particular problem informs us about connected notes. If you click on it, the problematic area will be displayed in the *main editor* and the faulty notes will be selected.

![](https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2F3MnLlUnV1KVXUc5uu0HY%2Fimage.png?alt=media\&token=7852d123-2986-4e05-a1f7-8431b39facae)

If you click *Correct* option you will see that "now" note was automatically shortened to avoid connected notes and that the number of errors decreased:

![](https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FI3ADNft6Njrvnh34wafP%2Fimage.png?alt=media\&token=518ed9d6-b3e9-4e9c-9c10-36d03870d360)

## Batch problem fixing

{% hint style="success" %}
You can apply automatic fixes to all problems at once
{% endhint %}

Instead of fixing errors one by one you can fix all at once by right-clicking on the category header (in this case *"Errors (2 items)*" and clicking *Correct* option there.

As a result all errors that have a safe fix available were fixed. The number of errors decreased to one.

If you right-click on the Errors category header again you will see that there are only problems with invasive solutions left:

![](https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FSatEpcA7L7nrfWoOBiQn%2Fimage.png?alt=media\&token=e56c277c-b4a5-43ce-99c0-9c0283b30999)

Since there is no other fix available, let's use the invasive option.&#x20;

You will see that the problem got resolved and the note with missing lyrics now got *\~* as lyrics. This solution is treated as risky because the editor has no way of knowing whether this is the correct lyrics for that note.

## No fix available

For some issues, especially warnings there may be no automatic fix available like in this example:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2F09nQ9WMGTirZmKd4jHue%2Fimage.png?alt=media&amp;token=e06634ab-1710-4485-abab-fecd1bd915b3" alt=""><figcaption></figcaption></figure>

Let's hover the mouse over this warning to learn more:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FxLl8YMQwaKaOgdPuj8Ja%2Fimage.png?alt=media&amp;token=e1751532-778d-48fa-badc-9cef8cc668d1" alt=""><figcaption></figcaption></figure>

So in order to get rid of this warning you should mark some notes as golden. You can learn more about golden notes bonus [here](/karedi/user-interface/middle-components/main-editor/managing-notes/note-types.md#golden-bonus).
