> 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/pdf-converter-for-notes/troubleshooting/history-log/conversion-and-error-logs.md).

# Conversion and error logs

The conversion log provides information on each conversion job initiated using the PDF toolbar icon. This information includes the number of selected documents in the conversion job, number of processed vs. failed documents, list of failed documents, a text file containing complete log and other relevant details.&#x20;

In order to use the conversion log, it first must be enabled in the General Settings of your SWING PDF Converter database (see below screenshot).

![](/files/-MlFb0Hx3dDUZaot-Xy3)

Once the conversion log is enabled, the conversion job reports will start appearing in the History Log section of your PDF Converter database (see below screenshot). The reports are categorized by date and by user.&#x20;

![](/files/-MlFbCF0UOqQXrsr5ciC)

In case one or more selected documents failed to convert, the number of failed documents will be displayed in the report view (see below screenshot). For more detailed information on the conversion job, open the report document.&#x20;

![](/files/-MlFbFCnRViP6SW53cQ0)

Each report contains all the relevant information about the documents that failed to convert during a particular conversion job, including a table showing a listing of the failed documents (see below screenshot). You can use this table to attempt converting the failed documents again (by hitting the Convert again button), or to locate the failed documents in your database (e.g. in order to send them to SWING Software support for further troubleshooting).

![](/files/-MlFbJCe8GUssFQKQ565)

Also, clicking on any document in the above table will provide you with further information on the error which occurred, including a direct link to the failed document in the original Notes database or mailbox. The below screenshot shows an example report on a document which failed to convert (the link to the document in the original database is highlighted).

![](/files/-MlFbNJ6xdJ3M3gq_lb4)

For convenience, the same error reports can also be found in the Errors view (see below screenshot) allowing you to locate and review errors faster.&#x20;

![](/files/-MlFbQv8FpVVMjip5WLX)


---

# 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/pdf-converter-for-notes/troubleshooting/history-log/conversion-and-error-logs.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.
