> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atla-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LangGraph flow showing exceptions?

> Why LangGraph subgraphs appear to have failures and how to interpret these traces

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:

* [Langfuse GitHub Discussion #6060](https://github.com/orgs/langfuse/discussions/6060)
* Similar issues reported across multiple observability platforms

## Support

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

* [Join our Discord](https://discord.gg/qFCMgkGwUK) for the latest updates
* [Schedule a call](https://calendly.com/atla-team/chat-to-atla) to discuss your specific LangGraph setup