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

Agent Node Displays Default Maximum Iterations as 3 but Triggers 'Cannot Be Empty' #13030

Open
5 tasks done
kevintsai1202 opened this issue Jan 25, 2025 · 1 comment
Open
5 tasks done
Labels
🐞 bug Something isn't working cloud When the version is cloud and it is a bug report
Milestone

Comments

@kevintsai1202
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

1.0-beta

Cloud or Self Hosted

Cloud

Steps to reproduce

When using the Agent Node, although the interface shows a default value of Maximum Iterations 3, a warning still appears in the upper right corner stating that Maximum Iterations cannot be empty.

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Copy link

dosubot bot commented Jan 25, 2025

The issue you're experiencing, where the Agent Node displays a default Maximum Iterations value of 3 but triggers a "Cannot Be Empty" warning, might be related to a mismatch between the displayed default value and the actual validation logic.

The default value for Maximum Iterations is set to 5 in the configuration files [1][2]. If the interface is showing 3, it could be due to a UI bug or a misconfiguration in the component responsible for rendering the default values. The validation logic ensures that the value is between 1 and 50, with a default of 5 [2].

To resolve this, you might want to check the component handling the display and validation of the Maximum Iterations field to ensure it aligns with the configuration. Additionally, verify if there are any recent changes or overrides in the code that might affect this behavior.

To continue talking to Dosu, mention @dosu.


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

@dosubot dosubot bot added cloud When the version is cloud and it is a bug report 🐞 bug Something isn't working labels Jan 25, 2025
@crazywoola crazywoola added this to the 1.0 milestone Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working cloud When the version is cloud and it is a bug report
Projects
None yet
Development

No branches or pull requests

2 participants