dify - 💡(How to fix) Fix Using Agent Policy ReAct to Call Tools (Workflow Published as a Tool) – No Process Output [1 comments, 2 participants]

TL;DR

The issue can be addressed by exploring alternative methods for streaming output of the calling process in the Agent node, potentially involving configuration changes or adjustments to the workflow.

Guidance

• Review the documentation for the Agent node and ReAct tool to see if there are any settings or options that enable streaming output.
• Investigate if the issue is specific to the ReAct tool or if it occurs with other tools as well, to determine if the problem lies with the tool or the Agent node.
• Consider reaching out to the community or support channels for Dify, as the issue may be related to the specific version (1.13.3) or a known limitation.
• Look into the differences between Function Calling and ReAct to understand why switching to Function Calling resulted in hallucinated data, which might provide clues to resolving the streaming output issue.

Example

No specific code snippet can be provided without more details on the implementation, but reviewing the Agent node and ReAct tool configurations is a good starting point.

Notes

The solution may depend on the specific requirements of the workflow and the capabilities of the tools being used. The issue might be version-specific or related to the self-hosted Docker environment.

Recommendation

Apply workaround: Given the lack of direct solutions, exploring workarounds such as adjusting the workflow, using different tools, or configuring the Agent node differently seems to be the most viable approach at this stage.