Running WF are taged as "Queued" instead of "running"

Questions
1

Describe the problem/error/question

Is it normal since n8n v1.56.0 that running execution are taged as “Queued” in execution tab ? Before it was “running” and we can saw since how long the execution was running.

image

For information, this happened when the WF is called by another WF (so for sub workflow).

Share the output returned by the last node

Information on your n8n setup

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

Hi @Kent1, sounds like it could be related to this change here feat(editor): Show new executions as `Queued` in the UI, until they actually start by netroy · Pull Request #10204 · n8n-io/n8n · GitHub which was released on v1.53.0

3

Possible indeed, but the thing is I’m 100% sur that my execution has started (because other sub workflows are executed) but they are all taged has “Queued” and not running.

4

Hello,

Any update on this issue ? As I said, sub workflow are executed but still showed as Queued and marked as succeeded or error at the end but never in running. For info, some of my workflow last 3min and never had status running.

1 Like
5

Hi @Kent1, could you maybe share your workflow or a bit more about it?

6

I attached an image where we can see one of my Workflow calling a subworkflow, and this subworkflow appears as “Queued” in execution tab.

image
image1120×281 39.3 KB

It never appear as running and after a while it appears as succeeded :

image

7

Hi @Kent1, sorry about the late reply. this sounds like a bug reported here: Workflows executed by workflows display as "Queued" in executions · Issue #10444 · n8n-io/n8n · GitHub. This has already been escalated internally and is being worked on :slight_smile:

8

Ok super if the problem is taken in charge. Thank for your help !

Could you let me know when this problem will be fix.

Thank again

1 Like