Skip to content
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

The conditional branch cannot obtain the output result of the previous iteration node #15209

Open
5 tasks done
cheneyyes opened this issue Mar 7, 2025 · 3 comments
Open
5 tasks done
Labels
🌊 feat:workflow Workflow related stuff.

Comments

@cheneyyes
Copy link

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

langgenius/dify-api:0.7.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Image

✔️ Expected Behavior

The conditional branch should obtain the output result of the previous iteration node, and the actual-value variable should be the outputs above

❌ Actual Behavior

The conditional branch cannot obtain the output result of the previous iteration node

@dosubot dosubot bot added the 🌊 feat:workflow Workflow related stuff. label Mar 7, 2025
Copy link

dosubot bot commented Mar 7, 2025

The issue you're experiencing, where the conditional branch node cannot obtain the output result of the previous iteration node, might be related to how data is passed between nodes in Dify workflows. In Dify, iteration nodes process input values formatted as list objects and output array variables. It's important to ensure that the data structure and types are correctly configured for the conditional branch to access these outputs.

Here are a few things you might want to check:

  1. Data Structure: Ensure that the output from the iteration node is indeed an array and that the conditional branch is set up to handle this type of data.

  2. Variable Configuration: Verify that the variables used in the conditional branch are correctly mapped to the outputs of the iteration node.

  3. Node Configuration: Double-check the configuration of the conditional branch node to ensure it is set to evaluate the correct variable and that the comparison operator is correctly applied.

If these aspects are correctly configured and the issue persists, it might be a bug specific to the version you are using (0.7.1). Unfortunately, I couldn't find specific known issues related to this in the available documentation. You might want to consider checking for any updates or patches that address this issue.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@cheneyyes
Copy link
Author

The workflow with the same configuration runs smoothly in the latest version of dify

Image

@cheneyyes
Copy link
Author

@Yeuoly plz,thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌊 feat:workflow Workflow related stuff.
Projects
None yet
Development

No branches or pull requests

1 participant