> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/hosting/scaling/concurrency-control.md).

# Control concurrency in Duaer

Limit how many production executions may run at the same time on self-hosted Duaer.
## Why limit concurrency

In regular mode, Duaer does not limit how many production executions may run at the same time. When triggers arrive faster than the machine can run them, too many concurrent executions thrash the event loop and the instance becomes slow or unresponsive.

With a concurrency limit, production executions over the cap wait in a queue instead of starting immediately. You can combine it with [queue mode](/hosting/scaling/queue-mode.md). Without queue mode, the cap still applies to this process.

## What it applies to

- Only production executions started from a webhook or trigger node. It does not apply to manual executions, sub-workflow executions, error workflow executions, or executions started from the CLI.
- You cannot retry queued executions. Cancelling or deleting a queued execution also removes it from the queue.
- On instance startup, Duaer resumes queued executions up to the concurrency limit and re-enqueues the rest.
- The cap is not a node count, and not the item count inside one workflow. Too many items can still fill memory inside a single execution — see [looping](/flow-logic/looping.md).
## Questions

### What does concurrency control limit in Duaer?

How many production executions (started from a webhook or trigger) run at the same time. It does not apply to manual runs, sub-workflows, or CLI starts. Past the cap, new executions wait instead of starting another wave that fills memory. You can combine it with queue mode.

