langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

WolframAlpha tool cannot work #1043

New Issue
Closed
opened 2026-02-21 17:29:40 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 17:29:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @bigzws on GitHub (Feb 8, 2024).

Originally assigned to: @takatost, @Yeuoly on GitHub.

Self Checks

Dify version

0.5.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The WolframAlpha tool has added an authorization prompt for an invalid appid. Clicking the button multiple times allows for the addition of authorization, but the func calling process cannot be used.
微信图片_20240208170605

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @bigzws on GitHub (Feb 8, 2024). Originally assigned to: @takatost, @Yeuoly on GitHub. ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to file this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). ### Dify version 0.5.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The WolframAlpha tool has added an authorization prompt for an invalid appid. Clicking the button multiple times allows for the addition of authorization, but the func calling process cannot be used. ![微信图片_20240208170605](https://github.com/langgenius/dify/assets/45476210/a15aad08-17c8-4e7f-a5a6-d58fb181ac9c) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 17:29:40 -05:00
yindo closed this issue 2026-02-21 17:29:40 -05:00
yindo commented 2026-02-21 17:29:40 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 8, 2024):

🤖

Hey there, @bigzws! 😄 Great to see you back! How's everything going on your end?

Based on the information you've provided, it seems like the issue you're experiencing with the WolframAlpha tool in Dify v0.5.4 is due to an invalid appid. The appid is a unique identifier provided by WolframAlpha that allows Dify to interact with the WolframAlpha API. If the appid is invalid, the WolframAlpha API will return an error, which is why you're seeing the authorization prompt.

The code in Dify is designed to try the request a maximum of three times before it stops trying. This is why you're able to click the button multiple times to add authorization, but the function calling process still can't be used. The function will stop trying to call the WolframAlpha API after three failed attempts.

To resolve this issue, you need to provide a valid appid. You can do this by updating the credentials_for_provider section of the wolframalpha.yaml file in your Dify installation. The appid field is of type secret-input and is required for the tool to function. Here is the relevant section from the YAML file:

credentials_for_provider:
  appid:
    type: secret-input
    required: true
    label:
      en_US: WolframAlpha AppID
      zh_Hans: WolframAlpha AppID
      pt_BR: WolframAlpha AppID
    placeholder:
      en_US: Please input your WolframAlpha AppID
      zh_Hans: 请输入你的 WolframAlpha AppID
      pt_BR: Please input your WolframAlpha AppID
    help:
      en_US: Get your WolframAlpha AppID from WolframAlpha, please use "full results" api access.
      zh_Hans: 从 WolframAlpha 获取您的 WolframAlpha AppID，请使用 "full results" API。
      pt_BR: Get your WolframAlpha AppID from WolframAlpha, please use "full results" api access.
    url: https://products.wolframalpha.com/api

You can get your WolframAlpha AppID from the WolframAlpha website, and it is recommended to use "full results" API access. Once you have your AppID, replace the placeholder text with your AppID.

I hope this helps! If you have any other questions or need further clarification, please let me know.

Sources

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot[bot] commented on GitHub (Feb 8, 2024): _🤖_ <!-- Greeting --> Hey there, @bigzws! 😄 Great to see you back! How's everything going on your end? <!-- Answer --> Based on the information you've provided, it seems like the issue you're experiencing with the WolframAlpha tool in Dify v0.5.4 is due to an invalid appid. The appid is a unique identifier provided by WolframAlpha that allows Dify to interact with the WolframAlpha API. If the appid is invalid, the WolframAlpha API will return an error, which is why you're seeing the authorization prompt. The code in Dify is designed to try the request a maximum of three times before it stops trying. This is why you're able to click the button multiple times to add authorization, but the function calling process still can't be used. The function will stop trying to call the WolframAlpha API after three failed attempts. To resolve this issue, you need to provide a valid appid. You can do this by updating the `credentials_for_provider` section of the `wolframalpha.yaml` file in your Dify installation. The `appid` field is of type `secret-input` and is required for the tool to function. Here is the relevant section from the YAML file: ```yaml credentials_for_provider: appid: type: secret-input required: true label: en_US: WolframAlpha AppID zh_Hans: WolframAlpha AppID pt_BR: WolframAlpha AppID placeholder: en_US: Please input your WolframAlpha AppID zh_Hans: 请输入你的 WolframAlpha AppID pt_BR: Please input your WolframAlpha AppID help: en_US: Get your WolframAlpha AppID from WolframAlpha, please use "full results" api access. zh_Hans: 从 WolframAlpha 获取您的 WolframAlpha AppID，请使用 "full results" API。 pt_BR: Get your WolframAlpha AppID from WolframAlpha, please use "full results" api access. url: https://products.wolframalpha.com/api ``` You can get your WolframAlpha AppID from the WolframAlpha website, and it is recommended to use "full results" API access. Once you have your AppID, replace the placeholder text with your AppID. I hope this helps! If you have any other questions or need further clarification, please let me know. ## Sources - [api/core/tools/provider/builtin/wolframalpha/tools/wolframalpha.py](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wolframalpha/tools/wolframalpha.py) - [api/core/tools/provider/builtin/wolframalpha/wolframalpha.yaml](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wolframalpha/wolframalpha.yaml) --- This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot.
yindo commented 2026-02-21 17:29:40 -05:00
Author
Owner
Copy Link
Copy Source

@Yeuoly commented on GitHub (Feb 9, 2024):

Could you please check your network and appid? it seems that everything is going fine in my case
image

@Yeuoly commented on GitHub (Feb 9, 2024): Could you please check your network and appid? it seems that everything is going fine in my case <img width="765" alt="image" src="https://github.com/langgenius/dify/assets/45712896/5da0a25f-1962-4306-824d-4802f764431f">
yindo commented 2026-02-21 17:29:40 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 15, 2024):

Seems fixed right now. If you encounter the same problem, please reopen this or dm me in wechat.

@crazywoola commented on GitHub (Feb 15, 2024): Seems fixed right now. If you encounter the same problem, please reopen this or dm me in wechat.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#1043
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?