> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/seascape-for-notes/troubleshooting/general-issues/conversion-log-in-case-of-a-notes-crash.md).

# View the conversion log in case of a Notes crash

A temporary log file is written on your hard disk which stores information on the progress of the export as well as the last processed document (which most likely caused Notes to crash).

This file can be found in the folder located in **%USERPROFILE%\AppData\Local\Temp\SWING Seascape** (the file name is random, so you will need to look for a .log file).

Once you’ve located this file you can send the information (and possibly the document which caused the crash) to SWING Support for further troubleshooting.


---

# 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.swingsoftware.com/seascape-for-notes/troubleshooting/general-issues/conversion-log-in-case-of-a-notes-crash.md?ask=<question>&goal=<endgoal>
```

`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.