# How are you handling LangChain and LangGraph breaking changes and debugging in multi-step workflows?

LangChain and LangGraph made it much easier to orchestrate a multi-step pipeline (transcription, summarization, caption generation, image generation) without custom state management, and the graph structure helped control step order with a human-approval checkpoint. But breaking changes between versions, hard-to-trace errors inside chains or nodes, and a steep learning curve have slowed things down. What practices or tooling have helped you manage upgrades and get clearer visibility into which step or node is failing?

##### Post Metadata
- Posted at: 4 months ago
- Author title: AI Enginner
- Net upvotes: 1



## Related Product
[LangChain](https://www.g2.com/products/langchain/reviews)

## Related Category
[Generative AI Infrastructure](https://www.g2.com/categories/generative-ai-infrastructure)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


