Reset/Modify Recursion Limit During Runtime

[JohnBPerkins]

When building graphs that include human-in-the-loop (HITL) nodes, the recursion limit often needs to be adjusted dynamically. Currently, the recursion limit is a fixed safeguard against infinite loops and deadlocks, but this can be overly restrictive when human input is involved. Introducing a way to reset or modify the recursion limit after exiting a HITL node would provide greater flexibility without compromising system integrity.

Problem Statement

• The recursion limit is static and does not reset after human intervention.
• Currently, the only way to adjust the recursion limit dynamically is to manually rewrite and handle it, which introduces unnecessary overhead.

Proposed Solution

• Allow dynamic modification of the recursion limit after exiting a HITL node, ensuring that the system can continue processing as intended.
• Introduce a method to reset or increment the recursion counter upon human intervention, acknowledging that a manual step has broken the recursion cycle.
• Provide an optional parameter or callback function that enables developers to adjust the limit based on workflow needs.

[cristianocca]

Would also be good to simply reset the recursion limit after a HITL / interrupt node, as this means the graph really "completed" and needs next steps (e.g., during multi-turn conversations where a sub-agent/graph may interrupt to ask for input)