Skip to content

When another workflow B encapsulated as a tool is invoked in workflow A, another error is triggered when B returns to A #14876

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 tasks done
auxpd opened this issue Mar 4, 2025 · 0 comments · Fixed by #14880
Labels
🐞 bug Something isn't working

Comments

@auxpd
Copy link
Contributor

auxpd commented Mar 4, 2025

Self Checks

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

Dify version

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Using a workflow for tool encapsulation, when core/workflow/nodes/llm/node.py LLMNode._run is called before the result_text is initialized, it causes the last output dict to reference an uninitialized variable

✔️ Expected Behavior

Exception information for workflow B can be returned correctly

❌ Actual Behavior

At the same time as the error is thrown, an "Failed to invoke tool: cannot access local variable 'result_text' where it is not associated with a value" error is also thrown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant