starweavingdream
starweavingdream
@Scallions I tried the solution given by the robot, and there were no particularly obvious problems after I cleared the data. If you want to try my method, I suggest...
@crazywoola Hello, after multiple tests, I found that the problem classification node located before the LLM node will trigger this issue when the number of categories exceeds one.
@ruanzhijian I'm sorry, I haven't managed to solve it either, and I'm also waiting for an official fix, as I'm not a professional Python developer. @laipz8200 Hello, I noticed this...
@laipz8200 Hello, this is a minimal workflow example I prepared. Since GitHub cannot upload .yml files, I changed the extension from .yml to .txt. Please change it back to .yml...
@laipz8200 Hello, may I ask if this issue can be fixed based on the files above?
This didn't solve my problem, where my problem was occurring was in the flow being interrupted when responding to the front end, not in the model not answering.
I found that the parsing failed because the api responded to `event: ping`
@laipz8200 @crazywoola Hello, could you please confirm if this issue can be reproduced? Also, do you have any related troubleshooting insights or solutions?
@laipz8200 @crazywoola Hello, I have tested version 1.3.0 and the issue still exists.
@crazywoola Sorry, I made a mistake. It's 1.2.0 😂