dify icon indicating copy to clipboard operation
dify copied to clipboard

Output of Variable Aggregator (Grouping) Not Properly Resolved in Custom External Tool within Workflow

Open yjc980121 opened this issue 1 month ago • 1 comments

Self Checks

  • [X] This is only for bug report, if you would like to ask a question, please head to Discussions.
  • [X] I have searched for existing issues search for existing issues, including closed ones.
  • [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • [X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.15.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When using the output of a variable aggregator (grouping) as input parameters for a custom external tool in a workflow, the variables are not being resolved correctly. This results in abnormal query parameters. Specifically:

The output of the variable aggregator is not resolved to its actual value as expected.

The custom external tool receives unresolved variable names instead of their actual values.

Abnormal query parameters cause the external tool to malfunction.

Steps to Reproduce:

Configure a variable aggregator (grouping) in the workflow and set its output variables.

Reference the output variables of the variable aggregator as input parameters in a custom external tool.

Run the workflow and observe the input parameters received by the custom external tool.

Notice that the input parameters remain unresolved variable names instead of actual values.

It is unclear whether Chatflow exhibits similar behavior. It is recommended to investigate this as well.

9CE34101-8AED-4941-B4F2-8B0C8D018127

54C6878E-8A5E-4b44-A322-84CC5C4EEB7A

the dsl file 钉钉日志.zip

✔️ Expected Behavior

The output of the variable aggregator should be resolved to actual values and passed as input parameters to the custom external tool.

❌ Actual Behavior

The output of the variable aggregator remains unresolved, causing the custom external tool to receive unresolved variable names.

yjc980121 avatar Jan 13 '25 09:01 yjc980121