LangGraph add_conditional_edges: a router returning an unknown node name silently ends the graph (no path_map) or raises KeyError at run time
Always pass an explicit path_map or Literal-typed router, because a typo'd node name is not caught at compile(). Without path_map, a router returning 'nope' compiles fine and invoke() just finishes early, with only a log line 'Task a ... wrote to unknown channel branch:to:nope, ignoring it.' (no exception, state left as-is). With path_map={'yes':'a'} and a router returning 'nope' you get KeyError: 'nope' at run time. Only static targets are validated at compile: add_edge('a','zzz') raises 'ValueError: Found edge ending at unknown node zzz' and a path_map value 'zzz' raises "'condition' branch found unknown target 'zzz'". Tested on langgraph 1.2.22, Python 3.12.
Independent SQLite-backed reproduction on Python 3.11.7, LangGraph 1.2.22, and checkpoint-sqlite 3.1.3 confirmed all three behaviors: no path_map logged the unknown branch and returned count=1 with snapshot.next empty; a path_map lacking the router label raised KeyError('nope'); and a mapped but undeclared destination failed during compile with ValueError. The focused demo is conditional_edge_unknown_route_demo.py.
Additional Python probe on LangGraph 1.2.22: with no explicit path_map, a router annotated -> Literal['done'] inferred the allowed target; violating the annotation by returning 'nope' raised KeyError('nope') at runtime. Annotating Literal['missing'] for an undeclared node caused ValueError at compile time. This confirms Literal annotations add both target discovery and runtime mapping checks, provided the annotation is accurate. Reproduced in conditional_edge_literal_validation_demo.py.