Error Encountered with Trigger Node Pinned Data and Enabled Runners in n8n

Questions
1

Hi team,

I’ve encountered an issue when executing a workflow that includes a trigger node with pinned data, while n8n is running with Runners enabled.

Environment configuration

N8N_RUNNERS_ENABLED=true
N8N_RUNNERS_MODE=internal
OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true

Error log

dev-n8n-worker     | Worker errored while running execution 9033 (job 6877)
dev-n8n            | Execution 9033 (job 6877) failed
dev-n8n            | AssertionError [ERR_ASSERTION]: a destinationNodeName is required for the new partial execution flow
dev-n8n            |     at WorkflowExecute.runPartialWorkflow2 (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:239:16)
dev-n8n            |     at ManualExecutionService.runManually (/usr/local/lib/node_modules/n8n/dist/manual-execution.service.js:104:40)
dev-n8n            |     at JobProcessor.processJob (/usr/local/lib/node_modules/n8n/dist/scaling/job-processor.js:158:59)
dev-n8n            |     at processTicksAndRejections (node:internal/process/task_queues:95:5)
dev-n8n            |     at Queue.<anonymous> (/usr/local/lib/node_modules/n8n/dist/scaling/scaling.service.js:115:17)
dev-n8n            | 
dev-n8n-worker     | a destinationNodeName is required for the new partial execution flow (execution 9033)
dev-n8n            | Problem with execution 9033: a destinationNodeName is required for the new partial execution flow. Aborting.
dev-n8n            | a destinationNodeName is required for the new partial execution flow (execution 9033)
dev-n8n            | Only running or waiting executions can be stopped and 9033 is currently error

Example for Reproduction

Notes

  • The error only occurs when the trigger node has pinned data.
  • If the trigger node has no pinned data or if data is pinned on a different node (e.g., “Edit Fields”), the execution works as expected.
  • If Runners are turned off and the trigger node has pinned data, the workflow executes without error.
2

Anyone experiencing same issues?

3

I’m running in exactly the same error when data is pinned for a trigger node. In my case it’s a form node trigger.

n8n version: 1.85.4.

  EXECUTIONS_MODE: queue
  N8N_DISABLE_PRODUCTION_MAIN_PROCESS: "false"
  OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS: "true"
  N8N_RUNNERS_ENABLED: "true"
4

This seems to be a problem in version 1.85.4. My n8n updated yesterday and since then everything stopped. Based on your errors I identified that there were a series of stopped executions that were constantly restarting (10 always active) in a workflow that had pine on the first node. The only way I was able to solve it was by deleting the problematic workflow, then everything went back to normal.

5

Still unsolved

6

Has the same problem.
n8n Version: 1.86.1

EXECUTIONS_MODE=queue
EXECUTIONS_TIMEOUT=3600
EXECUTIONS_TIMEOUT_MAX=7200
EXECUTIONS_DATA_MAX_AGE=60
EXECUTIONS_DATA_PRUNE=true
#OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true

Can run WF manually only with with commented OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true

7

Just updated to 1.88.0
The same.