You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using LangGraph to create an application and am using the NodeInterrupt class to create dynamic interrupts to allow human in the loop interactions in certain scenarios. I noticed that when I run a graph that gets interrupted and look at the traces in LangSmith the overall run status will have status succeeded but the node that got interrupted will have status Error.
I appreciate this is because the node started but did not complete but it feels wrong somehow when it is an intentional interrupt.
Here is some example code I ran and I have attached the LangSmith screenshot.
It would be nice if the status for the node showed something like "INTERRUPTED" instead of "ERROR" and maybe didn't show the full stacktrace of the NodeInterrupt Exception since it is an intended interruption.
The text was updated successfully, but these errors were encountered:
Issue you'd like to raise.
I am using LangGraph to create an application and am using the NodeInterrupt class to create dynamic interrupts to allow human in the loop interactions in certain scenarios. I noticed that when I run a graph that gets interrupted and look at the traces in LangSmith the overall run status will have status succeeded but the node that got interrupted will have status Error.
I appreciate this is because the node started but did not complete but it feels wrong somehow when it is an intentional interrupt.
Here is some example code I ran and I have attached the LangSmith screenshot.
Suggestion:
It would be nice if the status for the node showed something like "INTERRUPTED" instead of "ERROR" and maybe didn't show the full stacktrace of the NodeInterrupt Exception since it is an intended interruption.
The text was updated successfully, but these errors were encountered: