N8n Workflow Tool node/MCP Server Trigger behaviour - Not running sub-workflows on worker nodes

Hi @all-you-can-pete

The recommendation to use Webhooks + HTTP Request to get separate, distributed executions comes from community answers by n8n staff , not from the main docs pages.

Here are the relevant places:

  • The core docs for sub-workflows and queue mode don’t explicitly say “to distribute sub-workflows across workers, you must use webhooks.” [Sub-workflows docs; Queue mode docs]

The “recommended pattern” to use Webhook Trigger + HTTP Request for independent, distributed executions is documented in the official n8n workflow template “Pattern for Parallel Sub-Workflow Execution Followed by Wait-For-All Loop.” [Sub-workflows in queue mode; Parallel sub-workflow pattern]

If you’re looking for something to link as “documentation,” those two community threads and the template are currently the closest references available that I was able to find during my research.