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

common.modelProvider.parameterslnvali dRemoved:stop (unsupported) #15381

New Issue
Closed
opened 2026-02-21 19:21:28 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 19:21:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiaotang-12-ops on GitHub (Jul 15, 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

1.60

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Frequent switching of models:
common.modelProvider.parameterslnvalidRemoved:stop (unsupported)

✔️ Expected Behavior

Normal switching of models

❌ Actual Behavior

Frequent switching of models:
common.modelProvider.parameterslnvali
dRemoved:stop (unsupported)

Image
Originally created by @xiaotang-12-ops on GitHub (Jul 15, 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 [search for existing issues](https://github.com/langgenius/dify/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.60 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Frequent switching of models: common.modelProvider.parameterslnvalidRemoved:stop (unsupported) ### ✔️ Expected Behavior Normal switching of models ### ❌ Actual Behavior Frequent switching of models: common.modelProvider.parameterslnvali dRemoved:stop (unsupported) <img width="577" height="105" alt="Image" src="https://github.com/user-attachments/assets/e6063b0d-2690-4aab-b11e-aebef58ed4bb" />
yindo closed this issue 2026-02-21 19:21:28 -05:00
yindo commented 2026-02-21 19:21:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 15, 2025):

The warning "common.modelProvider.parametersInvalidRemoved:stop (unsupported)" appears when you switch between models and the new model doesn't support the stop parameter. Dify checks each model's allowed parameters during switching; if a parameter like stop isn't supported by the selected model, it's automatically removed and you get this notification. This is expected behavior and is designed to prevent invalid configuration—it's not a backend error, but a frontend warning to help you align parameters with model capabilities (source, source, source).

To avoid this, make sure only parameters supported by the target model are set before switching. If you often switch between models with different parameter support, consider clearing or resetting unsupported parameters (like stop) before switching, or check model documentation for compatibility. If this workflow is disruptive, you might want to suggest an enhancement for smoother parameter handling.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 15, 2025): <!-- Answer --> The warning "common.modelProvider.parametersInvalidRemoved:stop (unsupported)" appears when you switch between models and the new model doesn't support the stop parameter. Dify checks each model's allowed parameters during switching; if a parameter like stop isn't supported by the selected model, it's automatically removed and you get this notification. This is expected behavior and is designed to prevent invalid configuration—it's not a backend error, but a frontend warning to help you align parameters with model capabilities ([source](https://github.com/langgenius/dify/pull/21247), [source](https://github.com/langgenius/dify/blob/df89629e04e94954f63c91078f2d1fa62f9e67b1/web/utils/completion-params.ts), [source](https://github.com/langgenius/dify/blob/df89629e04e94954f63c91078f2d1fa62f9e67b1/web/app/components/workflow/nodes/llm/panel.tsx)). To avoid this, make sure only parameters supported by the target model are set before switching. If you often switch between models with different parameter support, consider clearing or resetting unsupported parameters (like stop) before switching, or check model documentation for compatibility. If this workflow is disruptive, you might want to suggest an enhancement for smoother parameter handling. <!-- 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/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=other)</sup>&nbsp;&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/issues/22421)
yindo commented 2026-02-21 19:21:28 -05:00
Author
Owner
Copy Link
Copy Source

@xiaotang-12-ops commented on GitHub (Jul 15, 2025):

当您在模型之间切换且新模型不支持 stop 参数时，会出现“common.modelProvider.parametersInvalidRemoved:stop (unsupported)”警告。Dify 会在切换过程中检查每个模型允许的参数；如果所选模型不支持像 stop 这样的参数，则会自动移除该参数，并向您发送此通知。这是预期行为，旨在防止无效配置——它不是后端错误，而是前端警告，旨在帮助您将参数与模型功能（source、source、source）对齐。

为避免这种情况，请确保在切换之前仅设置目标模型支持的参数。如果您经常在支持不同参数的模型之间切换，请考虑在切换之前清除或重置不受支持的参数（例如停止），或者查看模型文档以了解兼容性。如果此工作流程造成干扰，您可能需要建议改进，以便更顺畅地处理参数。

要回复，只需提及@dosu。

我做得怎么样？好|不相关|不正确|冗长|幻觉|举报🐛 |其他  加入 Discord 分享至X

Has the previously mentioned agent strategy not supporting calling MCP been resolved now？

@xiaotang-12-ops commented on GitHub (Jul 15, 2025): > 当您在模型之间切换且新模型不支持 stop 参数时，会出现“common.modelProvider.parametersInvalidRemoved:stop (unsupported)”警告。Dify 会在切换过程中检查每个模型允许的参数；如果所选模型不支持像 stop 这样的参数，则会自动移除该参数，并向您发送此通知。这是预期行为，旨在防止无效配置——它不是后端错误，而是前端警告，旨在帮助您将参数与模型功能（[source](https://github.com/langgenius/dify/pull/21247)、[source](https://github.com/langgenius/dify/blob/df89629e04e94954f63c91078f2d1fa62f9e67b1/web/utils/completion-params.ts)、[source](https://github.com/langgenius/dify/blob/df89629e04e94954f63c91078f2d1fa62f9e67b1/web/app/components/workflow/nodes/llm/panel.tsx)）对齐。 > > 为避免这种情况，请确保在切换之前仅设置目标模型支持的参数。如果您经常在支持不同参数的模型之间切换，请考虑在切换之前清除或重置不受支持的参数（例如停止），或者查看模型文档以了解兼容性。如果此工作流程造成干扰，您可能需要建议改进，以便更顺畅地处理参数。 > > _要回复，只需提及[@dosu](https://go.dosu.dev/dosubot)。_ > > 我做得怎么样？[好](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=great_response)|[不相关](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=irrelevant_answer)|[不正确](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=incorrect_sources)|[冗长](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=too_verbose)|[幻觉](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=hallucination)|[举报🐛](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=bug_report) |[其他](https://app.dosu.dev/response-feedback/b0cb2199-1edf-4d08-96a6-dcf08ceb04ad?feedback_type=other)  [![加入 Discord](https://camo.githubusercontent.com/d562c2df5e4567ea41d37f1d91a4da0839d8341037045b103b2da268998de17f/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![分享至X](https://camo.githubusercontent.com/4649f705e2396d6f328dbc8e800a0509c9c17b3b20253b36706c393df124b93d/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/22421) Has the previously mentioned agent strategy not supporting calling MCP been resolved now？
yindo commented 2026-02-21 19:21:28 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 15, 2025):

@dosu https://github.com/langgenius/dify/blob/816210d74491eccb950d22d877f084751158646b/web/app/components/workflow/nodes/llm/panel.tsx#L73-L92 It seems this warning is raised here.

@crazywoola commented on GitHub (Jul 15, 2025): @dosu https://github.com/langgenius/dify/blob/816210d74491eccb950d22d877f084751158646b/web/app/components/workflow/nodes/llm/panel.tsx#L73-L92 It seems this warning is raised here.
yindo commented 2026-02-21 19:21:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 15, 2025):

Yes, that warning is triggered in the referenced section of panel.tsx. When you switch models, the handleModelChange function calls fetchAndMergeValidCompletionParams to validate the current parameters against the new model's rules. If any parameters (like stop) are unsupported, they're removed and a warning is shown using Toast.notify, which is where you see the "common.modelProvider.parametersInvalidRemoved:stop (unsupported)" message. This is a frontend notification to help you keep parameters compatible with the selected model, not a backend error. You can see the relevant logic and flow in the code here: panel.tsx and completion-params.ts.

On your other question: official MCP support has been added, so agent nodes and applications can now invoke MCP tools directly (PR #20716). The parameter warning is unrelated to MCP or agent strategy issues.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 15, 2025): <!-- Answer --> Yes, that warning is triggered in the referenced section of panel.tsx. When you switch models, the handleModelChange function calls fetchAndMergeValidCompletionParams to validate the current parameters against the new model's rules. If any parameters (like stop) are unsupported, they're removed and a warning is shown using Toast.notify, which is where you see the "common.modelProvider.parametersInvalidRemoved:stop (unsupported)" message. This is a frontend notification to help you keep parameters compatible with the selected model, not a backend error. You can see the relevant logic and flow in the code here: [panel.tsx](https://github.com/langgenius/dify/blob/14f79ee6522d056e5fe602e2e27effa3ab68516d/web/app/components/workflow/nodes/llm/panel.tsx) and [completion-params.ts](https://github.com/langgenius/dify/blob/14f79ee6522d056e5fe602e2e27effa3ab68516d/web/utils/completion-params.ts). On your other question: official MCP support has been added, so agent nodes and applications can now invoke MCP tools directly ([PR #20716](https://github.com/langgenius/dify/pull/20716)). The parameter warning is unrelated to MCP or agent strategy issues. <!-- 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/d85030b4-edaf-4532-b6fe-e339484b2594?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d85030b4-edaf-4532-b6fe-e339484b2594?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d85030b4-edaf-4532-b6fe-e339484b2594?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d85030b4-edaf-4532-b6fe-e339484b2594?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d85030b4-edaf-4532-b6fe-e339484b2594?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d85030b4-edaf-4532-b6fe-e339484b2594?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d85030b4-edaf-4532-b6fe-e339484b2594?feedback_type=other)</sup>&nbsp;&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/issues/22421)
yindo commented 2026-02-21 19:21:29 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 15, 2025):

@xiaotang-12-ops This is a warning message, please see the bot's reply.

@crazywoola commented on GitHub (Jul 15, 2025): @xiaotang-12-ops This is a warning message, please see the bot's reply.
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
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#15381
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?