If you’re seeing exceptions or failures in your LangGraph traces, this is likely due to a known architectural pattern in LangGraph rather than actual errors in your code.

​
What’s Happening

LangGraph implements routing from subgraphs back to their parent graphs by intentionally raising internal exceptions in the subgraph. This is how LangGraph signals that execution should return to the parent graph and continue with the next step. From LangGraph’s perspective, this is normal operation. However, observability tools like Atla (and others) interpret these exceptions as failures since they appear as raised exceptions in the trace.

​
Why This Occurs

This is a known issue in the LangGraph ecosystem. You can find discussions about this behavior in various observability tool communities:

​
Support

This is an active area of development. To stay updated: