Skip to content

[Bug] Data does not pass through a reroute node: the next node gets None #52

Closed

Description

@bhowiebkr

Before submitting

  • I read the known problems in STATUS.md and searched open and closed issues.
  • I removed credentials, private paths and files I cannot share, also from any graph file I attach.

Program

From the source code

Area

Connections and reroute nodes

Observed behavior

Node A returns 'hello'. Its data output goes through a reroute node to input v of node B.
A runs before B by an execution connection. B gets None. With a direct data connection, B
gets 'hello'.

Reproduction

Built in code with the real NodeGraph and GraphExecutor, not by hand on the desktop. Ran 3
times; failed 3 times. The test test_reroute_passes_data in tests/test_reroute_data.py
builds the same graph (now marked xfail).

  1. Make node A: def a() -> str: return 'hello'.
  2. Make node B: def b(v: str) -> str: print('B got', repr(v)); return v.
  3. Connect exec_out of A to exec_in of B.
  4. Connect output_1 of A to a reroute node, and the reroute node to v of B.
  5. Run the graph. The output log shows B got None.

A graph file is not attached: a graph file with a connected reroute node does not open (see #51).

Expected behavior

B gets 'hello', as with a direct connection. A reroute node only changes the path of the
connection line.

Impact

Every graph that uses a reroute node on a data connection gives wrong results, with no error.

Build

From the source code, commit c04d1b2 with the uncommitted changes of the repository upgrade.

System

Windows 11, Python 3.13.14, PySide6 6.12.0.

Evidence

  • Observed: the output log shows B got None through the reroute node, and B got 'hello'
    with a direct connection.
  • Source-derived: GraphExecutor._execute_node_flow in
    src/pyflowgraph/execution/graph_executor.py sets the value of a reroute output only when it
    runs the reroute node. It runs a reroute node only as a start node (no input connection) or
    after another reroute node. A normal node follows only its execution outputs, so a reroute
    node with an input connection never runs.
  • Source-derived: BUG-2025-01-001: Reroute Nodes Return None in Execution #35 was closed as fixed. Its evidence was
    test_reroute_node_execution in tests/test_execution_engine.py, which copies the reroute
    code into the test and does not call the executor.
  • Proposed check: when a node reads an input from a reroute output, follow the reroute nodes
    back to the first non-reroute output pin.

Reported by

Claude Code agent (Claude Opus 5.5). Not yet reviewed by a person.

Activity

  1. added
    bugSomething isn't working
    executionGraph execution and data flow issues
    on Nov 15, 2026
  2. bhowiebkr commented on Nov 15, 2026

    @bhowiebkr
    OwnerAuthor

    Fixed in 5316e8c. A reroute node passes on the value of the output before it, also through chains of reroute nodes. Checked by tests/test_reroute_data.py and test_data_passes_through_a_chain_of_reroute_nodes in tests/test_undo_and_execution_fixes.py; all test files pass on Python 3.13 and 3.11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingexecutionGraph execution and data flow issues

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions