Workflow restarts from beginning when executing a single node after recent update

Questions
1

Hello n8n community,

I’ve noticed unexpected behavior since the latest n8n update that I’d like to report and see if others are experiencing the same issue.

Issue description:

When I manually execute a single node in a workflow (using the “Execute node” option), the entire workflow restarts from the beginning, even though the previous nodes have already been executed and have output data available.

Expected behavior:

I would expect the selected node to execute using the output data from the previously executed nodes, without re-running the entire workflow from scratch.

Context:

  • This behavior started appearing after the most recent n8n update

  • It happens consistently across different workflows

  • Previously, I could execute individual nodes downstream without re-triggering the entire workflow

Impact:

This makes debugging and testing specific nodes significantly more time-consuming, especially in longer workflows where earlier nodes might involve API calls or time-intensive operations.

Has anyone else encountered this issue? Is this an intended change in behavior, or could it be a bug introduced in the recent update?

Any insights or workarounds would be greatly appreciated.

Thank you!

Information on your n8n setup

  • n8n version: 1.115.0
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue mode, fliestream
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu
2

Hello all, I solved my problem by putting OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS to false in my docker-compose.

It’s a change of comportment since the 1.115.0

Best regards

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.