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
When calling the run api with stream=true , on a flow that uses the tool calling agent component, there is no stream_url in the answer. The api returns as if stream was set to false.
Reproduction
Just create a flow with the tool calling agent component, and try to run it through the api with stream=true
The issue you're experiencing, where the stream_url is not included in the response when using the tool calling agent component with stream=true, could be related to how the stream parameter is processed or how the tool calling agent component interacts with the streaming logic.
The build_stream_url method is responsible for generating the streaming URL when stream=true. It is called correctly in scenarios where the message is an instance of AsyncIterator or Iterator[1]. If the tool calling agent component does not produce a message in this form, the stream_url might not be generated.
To address this, you might want to check if the tool calling agent component is configured to support streaming and if it produces messages as iterators. Additionally, ensure that the component's logic aligns with the expected behavior for streaming, as any deviation might prevent the stream_url from being included in the response.
Bug Description
When calling the run api with
stream=true
, on a flow that uses thetool calling agent
component, there is nostream_url
in the answer. The api returns as ifstream
was set to false.Reproduction
Just create a flow with the
tool calling agent
component, and try to run it through theapi
withstream=true
Expected behavior
Instead of the call to block until the model returns the last message, the api should simply return reponse contaning a
stream_url
field.Who can help?
No response
Operating System
Arch Linux
Langflow Version
1.1.0 (commit efe6407)
Python Version
3.12
Screenshot
Flow File
No response
The text was updated successfully, but these errors were encountered: