惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

P
Proofpoint News Feed
Martin Fowler
Martin Fowler
The GitHub Blog
The GitHub Blog
B
Blog RSS Feed
U
Unit 42
阮一峰的网络日志
阮一峰的网络日志
量子位
GbyAI
GbyAI
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
云风的 BLOG
云风的 BLOG
小众软件
小众软件
博客园 - 三生石上(FineUI控件)
L
LangChain Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园_首页
IT之家
IT之家
V
Visual Studio Blog
Y
Y Combinator Blog
Blog — PlanetScale
Blog — PlanetScale
宝玉的分享
宝玉的分享
Apple Machine Learning Research
Apple Machine Learning Research
I
InfoQ
D
Docker
V
V2EX

Graph execution goes back to a previous node

Graph execution goes back to a previous node Graph execution goes back to a previous node Graph execution goes back to a previous node
Graph execution goes back to a previous node
ignacio · 2025-10-01 · via Graph execution goes back to a previous node

I’m running a graph with the architecture below, by which it should only execute the node get_product_id until a tool_condition calls it out of the React flow, and then it should go on with route_decision. But I’m getting an error: InvalidUpdateError("At key ‘route’: Can receive only one value per step. Use an Annotated key to handle multiple values.\nFor troubleshooting, visit: INVALID_CONCURRENT_GRAPH_UPDATE ")Traceback (most recent call last): When I look at the tracing (copied also below)...