UI Illusion: Executions list is hardcoded to fetch 10 items (Looks like a concurrency bottleneck)

Tips & Tricks
1

This topic was closed, but I found the real root cause that wasn’t mentioned there.

Hi everyone,

If you have already configured N8N_CONCURRENCY_PRODUCTION_LIMIT or your worker’s --concurrency flags properly but still see only exactly 10 executions running simultaneously on your dashboard, the bottleneck might not be your backend configuration at all. It could just be a visual limitation of the n8n UI.

By default, the Executions tab on the n8n dashboard hardcodes the internal API fetch requests (/rest/executions) to a limit of 10 records per page/refresh.

If you have 30 or 50 active parallel executions running seamlessly in the background, the UI will still only fetch and render the top 10 items. This easily creates a false impression that your workflows are locked or bottlenecked at 10 concurrent executions.

How to verify:

  1. Open your browser’s Developer Tools (F12) and go to the Network tab.

  2. Filter for Fetch/XHR and look for the executions?filter=... requests.

  3. Check the Preview/Response payload. You will likely see something like:

    JSON

    {
  "data": {
    "results": [...],
    "count": 10
  }
}

Even though the UI only displays 10 rows, the count property reveals the true number of active executions processed by your backend. You can even copy the request as fetch, manually increase the limit parameter to 40 or 50, and execute it in the Console to see all your active running instances.

Before tweaking your infrastructure or databases further, check your Network tab to ensure it isn’t just the UI pagination playing tricks on you!

Một vài từ khóa/lưu ý nhỏ nếu bạn muốn chỉnh sửa:

  • Câu trả lời này trực diện, chỉ ra ngay “Visual limitation” (Giới hạn hiển thị) thay vì cấu hình hệ thống.

  • Nó đưa ra giải pháp check Network tab rất cụ thể để những người sau có thể tự kiểm tra hệ thống của họ ngay lập tức mà không đoán già đoán non.

2

Welcome to the community @tai_nguyen1! Great catch — this trips up a lot of people who assume the UI reflects the real concurrency state. The Network tab trick is exactly the right way to verify it. Worth noting: you can also check the /rest/executions endpoint directly via the n8n REST API if you want to programmatically monitor active run counts without touching the browser dev tools.

1 Like