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

deepseek-chat tool call working not normal #12438

Closed
5 tasks done
leslie2046 opened this issue Jan 7, 2025 · 2 comments · Fixed by #12437 or #12463
Closed
5 tasks done

deepseek-chat tool call working not normal #12438

leslie2046 opened this issue Jan 7, 2025 · 2 comments · Fixed by #12437 or #12463
Labels
🐞 bug Something isn't working 🔨 feat:tools Tools for agent, function call related stuff.

Comments

@leslie2046
Copy link
Contributor

leslie2046 commented Jan 7, 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

0.14.2

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

  1. make a agent
  2. add a curenttime tool
  3. choose deepseek model based on openai_api_compatible provider or deepseek provider
  4. ask a quetion "what's the time now"

✔️ Expected Behavior

图片

❌ Actual Behavior

Sometimes there is no answer from LLM after tool call, and sometimes there is a correct answer after 5 iterations tool calls

d1381ff68fc5afc4bd0db24e47c2346
图片

Copy link

dosubot bot commented Jan 7, 2025

The issue you're experiencing with the deepseek-chat tool and the 'current_time' function seems to be related to how the tool is responding with multiple instances of "已使用 current_time" before providing the correct date or time. This behavior might be due to how the tool is integrated or how the deepseek model is handling the tool calls.

Here are a few things you might want to check or try:

  1. Tool Configuration: Ensure that the 'current_time' tool is correctly configured with the appropriate parameters, such as the desired time format and timezone. Misconfiguration might lead to unexpected behavior.

  2. Model Configuration: Verify the configuration settings for the deepseek model, such as temperature, top_p, and max_tokens, as these can affect how the model generates responses [1].

  3. Error Handling: Check if there are any error handling mechanisms in place that might be causing the tool to retry or respond multiple times. Dify provides features like retry on failure and error handling strategies that could be influencing the tool's behavior [2][3].

  4. Logs and Debugging: Utilize the logging capabilities of the Dify platform to observe the interactions and identify any anomalies in the tool's execution. This can help pinpoint where the issue might be occurring [4].

If these steps do not resolve the issue, it might be helpful to review the integration of the 'current_time' tool within the codebase to ensure there are no underlying bugs or misconfigurations.

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 🐞 bug Something isn't working 🔨 feat:tools Tools for agent, function call related stuff. labels Jan 7, 2025
@leslie2046
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🔨 feat:tools Tools for agent, function call related stuff.
Projects
None yet
1 participant