langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Model qwen3-coder-plus shows Function Calling support but Function Call mode is unavailable in Workflow Agent Node #893

New Issue
Closed
opened 2026-02-16 10:20:52 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:20:52 -05:00
Owner
Copy Link
Copy Source

Originally created by @ctysf on GitHub (Dec 22, 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 Dify issues & Dify Official Plugins, 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.11.0

Plugin version

qwen3-coder-plus

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have configured the model qwen3-coder-plus via an external provider (e.g., Alibaba Cloud). The Dify admin panel correctly shows that this model supports Function Calling (indicated by a green checkmark ✅ on the Model Provider page). However, when creating or editing a Workflow with an Agent Node and selecting qwen3-coder-plus as the model, the "Function Call" execution mode is not available in the dropdown list. Only "React" mode is selectable.

✔️ Error log

No response

Originally created by @ctysf on GitHub (Dec 22, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.0 ### Plugin version qwen3-coder-plus ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I have configured the model qwen3-coder-plus via an external provider (e.g., Alibaba Cloud). The Dify admin panel correctly shows that this model supports Function Calling (indicated by a green checkmark ✅ on the Model Provider page). However, when creating or editing a Workflow with an Agent Node and selecting qwen3-coder-plus as the model, the "Function Call" execution mode is not available in the dropdown list. Only "React" mode is selectable. ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:20:52 -05:00
yindo closed this issue 2026-02-16 10:20:52 -05:00
yindo commented 2026-02-16 10:20:53 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 22, 2025):

This behavior happens because the Workflow Agent Node UI determines available execution modes (like "Function Call") based on the strategy metadata provided by the model/plugin, not just the admin panel's capability check. For an external model such as qwen3-coder-plus, the strategy metadata must explicitly advertise function-calling support; otherwise, the UI will not show the "Function Call" option—even if the admin panel shows a green checkmark for Function Calling support. This is not hard-coded in the UI but is dynamically loaded from the plugin or provider's metadata. You may want to check the strategy metadata for your qwen3-coder-plus provider to ensure it declares function-calling capability as expected. More details on this logic can be found in the relevant code for the Workflow Agent Node configuration and backend validation of execution modes (source).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 22, 2025): <!-- Answer --> This behavior happens because the Workflow Agent Node UI determines available execution modes (like "Function Call") based on the strategy metadata provided by the model/plugin, not just the admin panel's capability check. For an external model such as qwen3-coder-plus, the strategy metadata must explicitly advertise function-calling support; otherwise, the UI will not show the "Function Call" option—even if the admin panel shows a green checkmark for Function Calling support. This is not hard-coded in the UI but is dynamically loaded from the plugin or provider's metadata. You may want to check the strategy metadata for your qwen3-coder-plus provider to ensure it declares function-calling capability as expected. More details on this logic can be found in the relevant code for the Workflow Agent Node configuration and backend validation of execution modes ([source](https://github.com/langgenius/dify/blob/42f7ecda126f50e8db9ae7bd0766e861beea516d/web/app/components/workflow/nodes/agent/use-config.ts#L28-L227)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/f9b63137-5fac-4023-80b6-0eadc2013366?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f9b63137-5fac-4023-80b6-0eadc2013366?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f9b63137-5fac-4023-80b6-0eadc2013366?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f9b63137-5fac-4023-80b6-0eadc2013366?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f9b63137-5fac-4023-80b6-0eadc2013366?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f9b63137-5fac-4023-80b6-0eadc2013366?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f9b63137-5fac-4023-80b6-0eadc2013366?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20behavior%20happens%20because%20the%20Workflow%20Agent%20Node%20UI%20determines%20available%20execution%20modes%20%28like%20%22Function%20Call%22%29%20based%20on%20the%20strategy%20metadata%20provided%20by%20the%20model/plugin%2C%20not%20just%20the%20admin%20panel%27s%20capability%20check.%20For%20an%20external%20model%20such%20as%20qwen3-coder-plus%2C%20the%20strategy%20metadata%20must%20explicitly%20advertise%20function-calling%20support%3B%20otherwise%2C%20the%20UI%20will%20not%20show%20the%20%22Function%20Call%22%20option%E2%80%94even%20if%20the%20admin%20panel%20shows%20a%20green%20checkmark%20for%20Function%20Calling%20support.%20This%20is%20not%20hard-coded%20in%20the%20UI%20but%20is%20dynamically%20loaded%20from%20the%20plugin%20or%20provider%27s%20metadata.%20You%20may%20want%20to%20check%20the%20strategy%20metadata%20for%20your%20qwen3-coder-plus%20provider%20to%20ensure%20it%20declares%20function-calling%20capability%20as%20expected.%20More%20details%20on%20this%20logic%20can%20be%20found%20in%20the%20relevant%20code%20for%20the%20Workflow%20Agent%20Node%20configuration%20and%20backend%20validation%20of%20execution%20modes%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/42f7ecda126f50e8db9ae7bd0766e861beea516d/web/app/components/workflow/nodes/agent/use-config.ts%23L28-L227%29%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/2311)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#893
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?