> 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 If Notes client crashes or freezes during a conversion job, the export log won't be generated but you can access the log file on your hard disk 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.swingsoftware.com/seascape-for-notes/troubleshooting/general-issues/conversion-log-in-case-of-a-notes-crash.md?ask=&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.