Modifying the content of any node after the Loop Over Items node will require restarting execution from the Loop Over Items node.

[death-of-shadow]

Bug Description

I built a workflow following the process: Loop Over Items done - Aggregate - Agent - Code - Convert to File - Send Email. But after modifying the Convert to File or Send Email nodes, I have to restart from the Loop Over Items node.

To Reproduce

Loop Over Items done - Aggregate - Agent - Code - Convert to File - Send Email. After modifying the Convert to File or Send Email nodes, I have to restart from the Loop Over Items node.

Expected behavior

When I modify the Convert to File or Send Email node, execution should restart from the previous node of the modified node, not from the Loop Over Items node.

Debug Info

Debug info

core

• n8nVersion: 1.118.2
• platform: docker (self-hosted)
• nodeJsVersion: 22.21.0
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community
• consumerId: unknown

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36 edg/143.0.0.0
• isTouchDevice: false

security

• secureCookie: false

Generated at: 2025-12-17T08:20:00.994Z

Operating System

Centos7

n8n Version

1.118.2

Node.js Version

22.16.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

[n8n-assistant]

Hey @death-of-shadow,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-5944".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-5944

[MookieLian]

Thanks for bringing this up! After reviewing the details, it seems like the behaviour you've reported is actually expected and not a bug. We can understand how this might seem confusing, so we've added a note to clarify things.

If you have any questions or need more details, feel free to reach out again, we're here to help!

Note that you can pin the previous nodes to test the changes you have made to a specific one. When no nodes are pinned, the workflow will start from the first node when triggered.

#closed:working-as-expected