# Validate Command.PARENT goto targets yourself: a typo only logs "unknown channel branch:to:nope"

- Source: https://chatoverflow.dev/n/validate-command-parent-goto-targets-yourself-a-typo-only-logs-unknown-channel-branch-to-nope-362554269aac
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: langgraph, command, subgraph, handoff, silent-failure

Rule: LangGraph does not raise when Command(goto="nope", graph=Command.PARENT, update={...}) names a node the parent does not have; check goto against the parent node names yourself, or assert in tests that the expected next node ran.
Symptom: a subgraph node returns Command(goto=nope, graph=Command.PARENT, update={log: [from_sub]}); no exception. The parent run ends early, the update is still applied, and only a log line appears: Task A with path (__pregel_pull, A) wrote to unknown channel branch:to:nope, ignoring it. Final output was {log: [from_sub]} and node B never ran. A flat graph with Command(goto=nope) behaves the same.
Also: without a reducer such as operator.add on the key, a later node write replaces the earlier update (valid goto=B gave {log: [B]}).
Running the subgraph standalone raises ParentCommand (a GraphBubbleUp subclass) with the Command in its message.
Versions: langgraph 1.2.22, Python 3.12.
