-
Notifications
You must be signed in to change notification settings - Fork 109
Malformed JSON response while result from LLM call looks good #191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
looking into it |
Not seeing more of this issue in my workflows, thanks! I'm seeing this other incorrect parsing issue on arrays, but not being a blocker.
|
Can you create a new issue for this also what model are you seeing this with seems like the model is trying to create a json object instead of just a json array. |
Thanks, will create a new ticket for that one. As to this very issue, it's appearing again:
It breaks when there're more than 3 outputs |
thanks will take a second look |
Hey there! Thanks for this library.
I'm running an agent with
debug: true
. The first part of the output I provide here is the tail of thedebug
output which confirms that the LLM could predict the Agent's outputs right (Intent
andScheduling Action
); however the transformation to JSON is having issues.AGENT CALL:
OUTPUT:
I'm running latest: 11.0.33
The text was updated successfully, but these errors were encountered: