From 7f48428d16fac75f9417c29fab685494c76fef0c Mon Sep 17 00:00:00 2001 From: Eugene Yurtsev Date: Wed, 11 Dec 2024 11:41:00 -0500 Subject: [PATCH] x --- docs/docs/concepts/human_in_the_loop.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/docs/concepts/human_in_the_loop.md b/docs/docs/concepts/human_in_the_loop.md index d2ad6fa49..7f7576501 100644 --- a/docs/docs/concepts/human_in_the_loop.md +++ b/docs/docs/concepts/human_in_the_loop.md @@ -395,14 +395,6 @@ The value of counter is: 2 ## Common Pitfalls -!!! warning - - Resuming from a interrupt is **different** from using Python's `input()` function, where execution resumes from the exact point where `input()` was called. - -A critical aspect of using `interrupt` is understanding how resuming works. When you resume execution, the graph execution starts from the **beginning** of the **graph node** where the `interrupt` was triggered. - -**All** code from the beginning of the node to the `interrupt` will be re-executed. - ### Side-effects Place code with side effects, such as API calls, **after** the `interrupt` to avoid duplication, as these are re-triggered every time the node is resumed.