Trying out the new Classify node (which is a great idea to combine an Agent + If/else!) and seeing a “Network error” message pop up at the top of the screen every time I run a test.
The outputs either go to an End node or to an Agent node. If I ask a question that should trigger the classification going to the End node, I can see in Evaluate, Post responses that it did classify the object, but there is nothing after that. If I enter something that classifies as “Other” which goes to the Agent, the Post response shows that it classified correctly, then it tries to go to the agent but that fails with this error:
We experienced an error while running the workflow. Sorry about that! You can retry your request, or contact us through our help center at help.openai.com if you keep seeing this error. (Please include the request ID 7ccb5573-2006-44bf-befc-c1efc92be841 in your message.)
4 Likes
In my workflow, the classify node DOES work if i put it for example DIRECTLY behind the start, but NOT, if i put it for example behind a guardrail node (which as a jailbreak guardrail of course should be the first node in the flow) - but I don’t understand why, because since the input for my classify is the workflow input, the guardrail node should not make any difference for the input?! or am I wrong here?
1 Like
OK; but at least the Jailbreak-Guardrail is no longer necessary anymore now, since you can just build a category in the classifier that includes all jailbreak-trials and leads to an end-node directly. so you can now implement the jailbreak-trials into the classifier-node as an additional type of “input”
2 Likes
Weird!
The funny thing is that if I export the workflow to Python I can run it on my laptop with no issue!
I wonder what the Guardrail is pushing into the context that is breaking things!
I guess it’s not a problem with the guardrail but with the new node … since it does not work in any other place in my flow EXCEPT as the first node after start. somehow the workflow input seems to be bugged in some way. a bit sad that there such a basic bug was not found/solved before rolling the node out, but I guess the problem will be solved within the next days/weeks.
2 Likes
Thanks @Moritz1.info for sharing the informative answer. It helps me a lot.
any news here? in my workflow, the classify-node still does not work when put at any place in the flow except for the first node … 