At a glance
- What happens at the limitEach project has a limit on how many flow runs execute at the same time.
- Change the limitOpen Project Settings, then General, and find Max Concurrent Jobs.
- If you embed ActivepiecesConcurrency limits can be set through the JWT used to provision users.
What happens at the limit
- Each project has a limit on how many flow runs execute at the same time.
- When the project hits it, new runs are queued, not dropped.
- Queued runs are retried with exponential backoff until a slot opens, so they always run, but they can be delayed while the project is at capacity.
Change the limit
- Open Project Settings, then General, and find Max Concurrent Jobs.
- Enter a limit, or leave it empty to use the default from your platform plan.
- Click Save.
If you embed Activepieces
- Concurrency limits can be set through the JWT used to provision users.
- The concurrencyPoolKey and concurrencyPoolLimit claims group several projects into one shared pool with one limit.
Updated 2026-11-02. General guidance, not advice for your situation; we scope each project in writing before any work starts.
Questions people ask first
Are runs over the limit lost?
No. Activepieces queues them and retries until a slot opens.
Where do I see queue depth?
On self-hosted Activepieces, a Prometheus endpoint reports queue job counts by state. Activepieces' docs say it is not available on Cloud.
Tell us what you need built.
Tell us the process and the tools involved, or call. We reply with questions or a written scope.
hello@pushbuild.com