How can I monitor active and queued worker counts in n8n Cloud?

Below is some guidance on how n8n Cloud handles concurrency and what you can (and cannot) monitor directly:

Active Executions vs. Workers

n8n Cloud manages production executions with a built‐in concurrency limit that depends on your subscription plan. In this context, “active executions” are the workflows currently running (or workers processing jobs) and any executions beyond that limit are queued automatically.

According to our documentation, you can see the number of active executions along with your plan's concurrency limit in the executions tab of a workflow or project. This count lets you know how many production executions are running at the moment.

Monitoring the Queue and Concurrency

Currently, n8n does not provide a built‐in method or API endpoint to programmatically retrieve the number of workers (or production executions) actively running versus those waiting in the queue. In Cloud:

• Active Executions: You can view these in the executions tab.
• Queued Executions: There isn’t a dedicated view or API to query the number of queued (waiting) executions from within workflows.

Because the concurrency control for production executions is managed automatically by n8n, the system will queue any execution that exceeds the limit and process them in FIFO order when capacity frees up.

Recommendations for Your Use Case

If you need to ensure that new webhooks (or job-triggering workflows) only start when you’re below your approximately 50-execution (or 50-worker) limit, consider these points:

1. Rely on n8n’s Built-In Concurrency Control:
   n8n Cloud enforces your plan’s concurrency limit automatically. This prevents more than the allowed number of production executions from running concurrently. For instance, on some plans the limit is set to 50.

2. Manual Monitoring via the UI:
   While you can’t script a check within a workflow, you can use the executions tab in the n8n editor to see the active executions and better understand your system’s current load.

3. Re-Architect the Workflow:
   If you require more granular control (such as delaying the start of new jobs), you might consider an external monitoring solution that queries metrics provided by n8n (if using self-hosted and queue mode, for example, the worker endpoints expose health and metrics; however, note that in n8n Cloud these are managed for you and might not be accessible in the same way).

4. Contact n8n Support:
   For complex scaling scenarios, especially if your workflows are causing unexpected load (e.g., triggering unintended webhook calls), reaching out to n8n support can help—there may be Cloud-specific considerations or configuration adjustments available to you.

Summary

• n8n Cloud automatically enforces a concurrency limit and uses a FIFO queue for executions that exceed that limit.
• The executions tab in n8n shows the number of active production executions and your concurrency limit.
• There isn’t a built-in method to check the queued count or to script prevention directly in workflows.
• For detailed workload management, consider relying on the built-in concurrency control or using external monitoring, and if needed, talk with n8n support for further guidance.

Hopefully, this clarifies how concurrency is managed on n8n Cloud and why your desired approach (checking active/queued worker counts programmatically within a workflow) isn’t directly supported.