> 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/general-issues/concurrent-execution-issues.md).

# Concurrent execution issues

Concurrent execution (multi-threading) is supported starting with SWING PDF Converter version 4 and higher.

Concurrent execution is not supported in SWING PDF Converter versions 3 or lower. This means that SWING PDF Converter will not work properly if for example two users are trying to run the conversion on a server at the same time.

Concurrent execution can be simulated by setting server's number of concurrent agents to 1. In this case all agent execution requests will be queued and executed one after the other.

Here's how to set number of concurrent agents to one:

* Open your server settings in Domino Administrator.
* In the left pane, select Server -> Current Server Document
* In the Current Server Document page select Server Tasks tab and then the Agent Manager tab.
* Set Max concurrent agents fields value to 1.
* Save and close server document


---

# 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/pdf-converter-for-notes/troubleshooting/general-issues/concurrent-execution-issues.md?ask=<question>&goal=<user_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.