Problem in node 'Workflow': The sub-workflow (WabZECBopnIZAz1t) cannot be called by this workflow - Only last subflow runs, others cancelled

Questions
1

When my parent workflow uses the Execute Workflow node (subflow) in a loop to call a child workflow multiple times (e.g., for different companies), n8n cancels most of the child executions. Only the last one actually runs; the rest are cancelled.

I want all subflow calls to be processed in parallel, not cancelled.

What I’ve tried

  • Set callerPolicy: “allWorkflows” and workflowCallerPolicy: “any” in the child workflow settings.

  • Made sure the child workflow is active and correctly selected in the parent.

  • Restarted all n8n containers and re-selected the child workflow in the parent node.

  • Still, when the parent loops and calls the child several times quickly, only the last call runs; the rest are cancelled.

What I want

Is there a way to make all subflow calls via Execute Workflow node run in parallel, without cancelling previous runs?

Information on my n8n setup

  • n8n version: 1.97.1

  • Database (default: SQLite): Postgres

  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue

  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker

  • Operating system: Ubuntu 22.04 (Docker host)

2

Maybe you need to share the workflow code on your end.

Screenshot_20250614_101545_JeHDFykY@2x
Screenshot_20250614_101545_JeHDFykY@2x1214×1284 55.1 KB

My test here seems normal.

Screenshot_20250614_101549_ey9N4srM@2x
Screenshot_20250614_101549_ey9N4srM@2x1802×680 50.6 KB

3

it’s working fine when it comes to sending the request — the issue seems to be on the receiving end.

just wanted to confirm if there’s a known issue or limitation where a subflow might drop executions if the same parent flow sends another job while the previous one is still running (say, if those executions take 3–10 seconds)?

image
image2240×1248 243 KB