Why do workflow tools need to return JSON and TEXT two same results? #10794
Replies: 2 comments 1 reply
-
I found two similar discussions regarding the issue of workflow tools returning duplicate results in JSON and TEXT formats:
These discussions might provide additional insights or context regarding the rationale behind this design choice and any potential solutions or workarounds. |
Beta Was this translation helpful? Give feedback.
-
If you want to use it in the agent, the agent will take all things it produces, such as json message and text message, however you can choose the answer you want in workflow. There is a workaround, you can publish the workflow as a tool, and return text or json message only, then you won't get the duplicated message I think. |
Beta Was this translation helpful? Give feedback.
-
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Workflow tools return JSON and TEXT two same results, are there any special scenarios to consider?
This will cause the FunctionCallAgentRunner to provide the duplicate tool results to the LLM"s API, which will take up twice the number of tokens.
2. Additional context or comments
If two same result is no special purpose, this logic will bring more performance consumption, more token consumption and fees, and more LLM context occupation
3. Can you help us with this feature?
Beta Was this translation helpful? Give feedback.
All reactions