Describe the bug

After experimenting with a Parallel architecture in AgentFlow V2 (based on the official documentation),
the same project started executing nodes twice.

Even after abandoning the Parallel architecture and simplifying the flow,
the issue persists within the same project:
some nodes are still executed twice during a single flow execution.

The problem was originally observed when using a Parallel setup with non-LLM nodes
(Splitter nodes combined with HTTP Request nodes),
but after removing that architecture, duplicated executions continue to happen.

This suggests that the project/flow might remain in an inconsistent state
after using the Parallel pattern in AgentFlow V2.

To Reproduce

1. Create a new AgentFlow V2 project
2. Implement a Parallel architecture as shown in the official documentation
3. Use Splitter nodes to create parallel branches
4. In each branch, use non-LLM nodes (e.g. HTTP Request nodes)
5. Run the flow and observe duplicated node executions
6. Remove or abandon the Parallel architecture
7. Simplify the flow (even with a linear setup)
8. Run the same project again
9. Observe that some nodes are still executed twice

Expected behavior

Each node should be executed exactly once per flow execution.

Removing the Parallel architecture should restore normal behavior,
with no duplicated executions in the same project.

Screenshots

test.json

Flow

No response

Use Method

Flowise Cloud

Flowise Version

No response

Operating System

None

Browser

Chrome

Additional context

Once this issue occurs, duplicating the project is not enough to resolve it.
The only way to get out of this state is to create a completely new project
and manually rebuild the entire flow.

Exporting the project also carries the bug with it, so importing the exported
JSON into a new project does NOT fix the problem.

I have also attached the JSON of a portion of the project to help with debugging.