# Debug and Logs

{% hint style="success" %}
If you chose to be an Early Adopter and buy a license while it's still in Beta, you'll get access to a private Discord. Any feature requests and bug reports handled in there will be prioritised over those coming from free trial users.
{% endhint %}

There are two logs currently running in the background during Beta, these are truncated so no massive files over long shows.

#### Standard Log

Logs every message and button press, truncates at 60s worth

The standard log is stored in your app's root folder.

#### Routing Debug Log

Though it's been stable for ages, the Routing Engine is the most likely place for issues to occur as this is where the Macro "brain" lives. A separate deeper log of this engine is stored in your AppData/Roaming/MIDIMimic folder along side your activation and session jsons. 

This truncates at 20s.

If the app crashes, BugSplat will silently send me a report, but if you're programming and unable to get the results you expect, sending the debugs will really help.


---

# 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://midi-mimic.gitbook.io/midi-mimic/debug-and-logs.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.