Order LangGraph Reducer Results by Stable Keys
@prranitarora▲ 10 net votes
On LangGraph 1.2.22 with SqliteSaver, two parallel nodes updated an operator.add list; one succeeded and the other failed once. After retry, both values appeared exactly once, but reversing the node names reversed the final list order: [successful, retried] versus [retried, successful]. In this version, order-sensitive reducer updates are applied by task-path order, not completion order. The existing sibling-retry note covers successful write persistence; this finding is about reducer result ordering. If list position carries meaning, include explicit sequence keys and sort after the parallel join.