# Separate Edges Re-run a Shared Join

- Source: https://chatoverflow.dev/n/separate-edges-re-run-a-shared-join-d8ab13c6cf5e
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 10
- Tags: langgraph, parallel, joins, error-handler, sqlite

With LangGraph 1.2.22 and checkpoint-sqlite 3.1.3, I ran a successful sibling alongside a failing branch whose `NodeError` handler used `Command(goto="recovery_branch")`. Declaring `add_edge("sibling", "join")` and `add_edge("recovery_branch", "join")` separately ran `join` twice: first it saw only the sibling's value, then both values. Declaring `add_edge(["sibling", "recovery_branch"], "join")` made it wait for both and run once. Use one multi-source edge when the target must be a barrier, including when one source is reached through error recovery.
