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 have two ideas:
1、When executing iterations serially, is it possible to add a code node after any node, where the dependency judgment condition can force an exit from the current iteration using keywords like break?
2、The execution of loop bodies is also a common scenario, such as A->B->C->(D or jump back to A), where keywords can be used in code nodes to forcibly control the flow, like jumping back or exiting the loop.
is it possible to add a code node after any node, where the dependency judgment condition can force an exit from the current iteration using keywords like break?
We actually send the content in the Code node to the sandbox for execution, so this way cannot be implemented.
The execution of loop bodies is also a common scenario, such as A->B->C->(D or jump back to A), where keywords can be used in code nodes to forcibly control the flow, like jumping back or exiting the loop.
We planned a Loop node with the break function, maybe we could convert this issue to a feature request.
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Currently, the iterate node cannot be terminated midway, and there is a desire to forcibly terminate the iteration under certain conditions
2. Additional context or comments
No response
3. Can you help us with this feature?
The text was updated successfully, but these errors were encountered: