What's the difference between queued and waiting executions?

[StocktonF]

I’ve just started to see “queued” execution status in addition to “waiting”.

Is it something to do with delay’s set in a workflow?

Debug info

core

• n8nVersion: 1.54.2
• platform: docker (self-hosted)
• nodeJsVersion: 20.15.0
• database: postgres
• executionMode: scaling
• concurrency: -1
• license: community
• consumerId: unknown

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

Generated at: 2024-08-15T18:04:00.491Z

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[StocktonF]

@StocktonF

Debug info

core

• n8nVersion: 1.54.2
• platform: docker (self-hosted)
• nodeJsVersion: 20.15.0
• database: postgres
• executionMode: scaling
• concurrency: -1
• license: community
• consumerId: unknown

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

Generated at: 2024-08-15T18:04:00.491Z

Debug info

core

• n8nVersion: 1.54.2
• platform: docker (self-hosted)
• nodeJsVersion: 20.15.0
• database: postgres
• executionMode: scaling
• concurrency: -1
• license: community
• consumerId: unknown

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

Generated at: 2024-08-15T18:04:00.491Z

[aya]

Hi @StocktonF thanks for posting!

• Queued executions: there is always a short delay between when executions are created and when they actually start running. We used to show the status as Running but recently made changes to call it Queued instead. See here:
  feat(editor): Show new executions as `Queued` in the UI, until they actually start by netroy · Pull Request #10204 · n8n-io/n8n · GitHub
• Waiting executions: on hold because something else needs to happen first

That’s my understanding! Hope that helps.

[Olexiy_Zalevskyi]

Hey!
sounds very interessting. What is the actual concurrency limit for parallel workflows and where can I change it? Use 1.54.4 OnPrem
Thanks in advance!
Cheers

[aya]

Hi @Olexiy_Zalevskyi, n8n doesn’t set any concurrency limits by default if you use a self-hosted version of n8n in regular mode. But you can change this by setting the N8N_CONCURRENCY_PRODUCTION_LIMIT env variable. You can find more info here: Concurrency control | n8n Docs