silicon custom model manage #907

New Issue

Closed

opened 2026-02-16 10:20:55 -05:00 by yindo · 2 comments

yindo commented 2026-02-16 10:20:55 -05:00

Owner

Copy Link

Copy Source

Originally created by @MJ-0414 on GitHub (Dec 29, 2025).

Self Checks

• I have read the Contributing Guide and Language Policy.
• 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, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

V1.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I add custom model credentials in Silicon and the addition is successful, I cannot select the newly added custom model in the LLM node. The new model is “Qwen/Qwen3-VL-32B-Instruct” and "Qwen/Qwen3-VL-235B-A22B-Instruct"

✔️ Expected Behavior

When I can select the newly added custom model in the LLM node of the workflow

❌ Actual Behavior

No response

Originally created by @MJ-0414 on GitHub (Dec 29, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version V1.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When I add custom model credentials in Silicon and the addition is successful, I cannot select the newly added custom model in the LLM node. The new model is “Qwen/Qwen3-VL-32B-Instruct” and "Qwen/Qwen3-VL-235B-A22B-Instruct" <img width="787" height="406" alt="Image" src="https://github.com/user-attachments/assets/48e856e8-a25f-4181-b5f0-6d8d6d806bed" /> ### ✔️ Expected Behavior When I can select the newly added custom model in the LLM node of the workflow ### ❌ Actual Behavior _No response_

yindo added the bug label 2026-02-16 10:20:55 -05:00

yindo closed this issue 2026-02-16 10:20:55 -05:00

yindo commented 2026-02-16 10:20:55 -05:00

Author

Owner

Copy Link

Copy Source

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

This is a known issue in v1.11.1: after adding custom model credentials in Silicon, the new model may not appear in the LLM node selection because the UI state does not refresh properly and/or the model credential is not explicitly added to the active model list. A recent fix (PR langgenius/dify#30250, merged after v1.11.1) ensures that after adding or editing a custom model, the UI and backend state are updated so the model becomes selectable.

In v1.11.1, you may need to manually ensure that after adding credentials, the model is added to the active model list (not left in a pending state). If the UI does not reflect the new model, try refreshing the page or reloading the workflow editor. If the issue persists, upgrading to a version that includes this fix is the most reliable solution.

The backend logic requires that the model credential be explicitly added to the model list for it to become available for selection; otherwise, it will not show up in the LLM node even if credentials were added successfully. This is handled by the add_model_credential_to_model_list method in the backend service. If you have access, you can check the model's status in the backend or database to confirm whether it is active or still pending.

Reference:

• PR langgenius/dify#30250 - fix custom tool content is not update
• ModelProviderService code

To reply, just mention @dosu.

---

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

   

@dosubot[bot] commented on GitHub (Dec 29, 2025): <!-- Answer --> This is a known issue in v1.11.1: after adding custom model credentials in Silicon, the new model may not appear in the LLM node selection because the UI state does not refresh properly and/or the model credential is not explicitly added to the active model list. A recent fix ([PR langgenius/dify#30250](https://github.com/langgenius/dify/pull/30250), merged after v1.11.1) ensures that after adding or editing a custom model, the UI and backend state are updated so the model becomes selectable. In v1.11.1, you may need to manually ensure that after adding credentials, the model is added to the active model list (not left in a pending state). If the UI does not reflect the new model, try refreshing the page or reloading the workflow editor. If the issue persists, upgrading to a version that includes this fix is the most reliable solution. The backend logic requires that the model credential be explicitly added to the model list for it to become available for selection; otherwise, it will not show up in the LLM node even if credentials were added successfully. This is handled by the `add_model_credential_to_model_list` method in the backend service. If you have access, you can check the model's status in the backend or database to confirm whether it is active or still pending. Reference: - [PR langgenius/dify#30250 - fix custom tool content is not update](https://github.com/langgenius/dify/pull/30250) - [ModelProviderService code](https://github.com/langgenius/dify/blob/7a5d2728a11f065dcaaf7719b165d845fd13db4b/api/services/model_provider_service.py#L23-L576) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- ^{How did I do? [Good](https://app.dosu.dev/response-feedback/06fdf14d-3f3d-4367-a7b3-5c3d8afc4361?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/06fdf14d-3f3d-4367-a7b3-5c3d8afc4361?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/06fdf14d-3f3d-4367-a7b3-5c3d8afc4361?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/06fdf14d-3f3d-4367-a7b3-5c3d8afc4361?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/06fdf14d-3f3d-4367-a7b3-5c3d8afc4361?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/06fdf14d-3f3d-4367-a7b3-5c3d8afc4361?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/06fdf14d-3f3d-4367-a7b3-5c3d8afc4361?feedback_type=other)} [](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20in%20v1.11.1%3A%20after%20adding%20custom%20model%20credentials%20in%20Silicon%2C%20the%20new%20model%20may%20not%20appear%20in%20the%20LLM%20node%20selection%20because%20the%20UI%20state%20does%20not%20refresh%20properly%20and/or%20the%20model%20credential%20is%20not%20explicitly%20added%20to%20the%20active%20model%20list.%20A%20recent%20fix%20%28%5BPR%20%2330250%5D%28https%3A//github.com/langgenius/dify/pull/30250%29%2C%20merged%20after%20v1.11.1%29%20ensures%20that%20after%20adding%20or%20editing%20a%20custom%20model%2C%20the%20UI%20and%20backend%20state%20are%20updated%20so%20the%20model%20becomes%20selectable.%0A%0AIn%20v1.11.1%2C%20you%20may%20need%20to%20manually%20ensure%20that%20after%20adding%20credentials%2C%20the%20model%20is%20added%20to%20the%20active%20model%20list%20%28not%20left%20in%20a%20pending%20state%29.%20If%20the%20UI%20does%20not%20reflect%20the%20new%20model%2C%20try%20refreshing%20the%20page%20or%20reloading%20the%20workflow%20editor.%20If%20the%20issue%20persists%2C%20upgrading%20to%20a%20version%20that%20includes%20this%20fix%20is%20the%20most%20reliable%20solution.%0A%0AThe%20backend%20logic%20requires%20that%20the%20model%20credential%20be%20explicitly%20added%20to%20the%20model%20list%20for%20it%20to%20become%20available%20for%20selection%3B%20otherwise%2C%20it%20will%20not%20show%20up%20in%20the%20LLM%20node%20even%20if%20credentials%20were%20added%20successfully.%20This%20is%20handled%20by%20the%20%60add_model_credential_to_model_list%60%20method%20in%20the%20backend%20service.%20If%20you%20have%20access%2C%20you%20can%20check%20the%20model%27s%20status%20in%20the%20backend%20or%20database%20to%20confirm%20whether%20it%20is%20active%20or%20still%20pending.%0A%0AReference%3A%20%20%0A-%20%5BPR%20%2330250%20-%20fix%20custom%20tool%20content%20is%20not%20update%5D%28https%3A//github.com/langgenius/dify/pull/30250%29%0A-%20%5BModelProviderService%20code%5D%28https%3A//github.com/langgenius/dify/blob/7a5d2728a11f065dcaaf7719b165d845fd13db4b/api/services/model_provider_service.py%23L23-L576%29)&nbsp;[](https://go.dosu.dev/discord-bot)&nbsp;[](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/30337)

yindo commented 2026-02-16 10:20:55 -05:00

Author

Owner

Copy Link

Copy Source

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

This is a known issue in Dify v1.11.1: after adding custom model credentials in Silicon, the new model may not appear in the LLM node because the UI and backend state do not always sync properly, and the model credential might not be added to the active model list. A fix for this was merged after v1.11.1 (PR #30250), which ensures that after adding or editing a custom model, the UI and backend state are updated so the model becomes selectable.

For v1.11.1, try these steps:

• Refresh the page or reload the workflow editor after adding a custom model.
• Make sure the model is in the active model list (not pending) in the backend or database.
• Confirm the model supports required capabilities (function call/ReACT) and is fully configured as a system inference model.
• Remove or configure any other model plugins (like Ollama or vLLM) that are unconfigured or unavailable, as these can interfere with model selection.
• Double-check environment variables like POSITION_PROVIDER_INCLUDES and POSITION_PROVIDER_EXCLUDES.
• Restart Docker containers after changes and check backend logs for errors.

If the issue persists, upgrading to a version that includes the fix from PR #30250 is the most reliable solution. For more details, see this issue.

To reply, just mention @dosu.

---

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

  

@dosubot[bot] commented on GitHub (Dec 29, 2025): <!-- Answer --> This is a known issue in Dify v1.11.1: after adding custom model credentials in Silicon, the new model may not appear in the LLM node because the UI and backend state do not always sync properly, and the model credential might not be added to the active model list. A fix for this was merged after v1.11.1 ([PR #30250](https://github.com/langgenius/dify/pull/30250)), which ensures that after adding or editing a custom model, the UI and backend state are updated so the model becomes selectable. For v1.11.1, try these steps: - Refresh the page or reload the workflow editor after adding a custom model. - Make sure the model is in the active model list (not pending) in the backend or database. - Confirm the model supports required capabilities (function call/ReACT) and is fully configured as a system inference model. - Remove or configure any other model plugins (like Ollama or vLLM) that are unconfigured or unavailable, as these can interfere with model selection. - Double-check environment variables like `POSITION_PROVIDER_INCLUDES` and `POSITION_PROVIDER_EXCLUDES`. - Restart Docker containers after changes and check backend logs for errors. If the issue persists, upgrading to a version that includes the fix from PR #30250 is the most reliable solution. For more details, see [this issue](https://github.com/langgenius/dify/issues/30337). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- ^{How did I do? [Good](https://app.dosu.dev/response-feedback/0b933c0e-ae6f-4e59-831a-9c3136bccd39?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0b933c0e-ae6f-4e59-831a-9c3136bccd39?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0b933c0e-ae6f-4e59-831a-9c3136bccd39?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0b933c0e-ae6f-4e59-831a-9c3136bccd39?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0b933c0e-ae6f-4e59-831a-9c3136bccd39?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0b933c0e-ae6f-4e59-831a-9c3136bccd39?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0b933c0e-ae6f-4e59-831a-9c3136bccd39?feedback_type=other)} [](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20in%20Dify%20v1.11.1%3A%20after%20adding%20custom%20model%20credentials%20in%20Silicon%2C%20the%20new%20model%20may%20not%20appear%20in%20the%20LLM%20node%20because%20the%20UI%20and%20backend%20state%20do%20not%20always%20sync%20properly%2C%20and%20the%20model%20credential%20might%20not%20be%20added%20to%20the%20active%20model%20list.%20A%20fix%20for%20this%20was%20merged%20after%20v1.11.1%20%28%5BPR%20%2330250%5D%28https%3A//github.com/langgenius/dify/pull/30250%29%29%2C%20which%20ensures%20that%20after%20adding%20or%20editing%20a%20custom%20model%2C%20the%20UI%20and%20backend%20state%20are%20updated%20so%20the%20model%20becomes%20selectable.%0A%0AFor%20v1.11.1%2C%20try%20these%20steps%3A%0A-%20Refresh%20the%20page%20or%20reload%20the%20workflow%20editor%20after%20adding%20a%20custom%20model.%0A-%20Make%20sure%20the%20model%20is%20in%20the%20active%20model%20list%20%28not%20pending%29%20in%20the%20backend%20or%20database.%0A-%20Confirm%20the%20model%20supports%20required%20capabilities%20%28function%20call/ReACT%29%20and%20is%20fully%20configured%20as%20a%20system%20inference%20model.%0A-%20Remove%20or%20configure%20any%20other%20model%20plugins%20%28like%20Ollama%20or%20vLLM%29%20that%20are%20unconfigured%20or%20unavailable%2C%20as%20these%20can%20interfere%20with%20model%20selection.%0A-%20Double-check%20environment%20variables%20like%20%60POSITION_PROVIDER_INCLUDES%60%20and%20%60POSITION_PROVIDER_EXCLUDES%60.%0A-%20Restart%20Docker%20containers%20after%20changes%20and%20check%20backend%20logs%20for%20errors.%0A%0AIf%20the%20issue%20persists%2C%20upgrading%20to%20a%20version%20that%20includes%20the%20fix%20from%20PR%20%2330250%20is%20the%20most%20reliable%20solution.%20For%20more%20details%2C%20see%20%5Bthis%20issue%5D%28https%3A//github.com/langgenius/dify/issues/30337%29.)&nbsp;[](https://go.dosu.dev/discord-bot)&nbsp;[](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/2347)

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

feat/3479-gemini-flash-models

dependabot/uv/tools/chart/uv-cdf8d38825

feat/moonshot-kimi-k3-k27-code

feat/gemini-system-instruction-semantics

fix/gemini-text-system-parts

dosu/doc-update-3436

feat/openai-gpt-5-6-support

fix/outlook-trigger-readme-permissions

fix/microsoft-oauth-datasource-tenant

fix/byteplus-api-base-url-label

feat/ark-video-generation-custom-models

fix/openai-stream-reasoning-thinking

fix/skip-live-tests-missing-keys

codex/enhance-discord-integrations

codex/harden-trigger-oauth-permissions

update-lemonade-default-port

codex/fix-pr-review-ci

feat/ark-multimodal-polling

copilot/update-mineru-3x-plugin-file-types

feat/action-security-fix

feat/claude-fable5

codex/fix-ollama-model-category

codex/upgrade-ollama-latest

feat/minimax-m3

codex/refine-plugin-readmes

fix/fireworks-model-label-zh-hans

chore/version-bump-plugins-batch-06

chore/version-bump-plugins-batch-05

chore/version-bump-plugins-batch-04

chore/version-bump-plugins-batch-03

chore/version-bump-plugins-batch-02

fix/plugin-sdk-i18n-fields

chore/version-bump-plugins-batch-01

chore/dependencies-high-priority

chore/dependencies-medium-priority

chore/dependencies-low-priority-clean

chore/dependencies-low-priority

fix/tongyi-align-deepseek-model-metadata

codex/update-openrouter-models

codex/azure-ai-studio-cjk-version-bump

feat/ernie-image-tool

claude/cranky-thompson-b6a281

fix/remove-unavailable-volcengine-models

fix/legacy-plugin-daemon-compatibility

copilot/add-deepseek-v4-to-openrouter

codex/merge-tongyi-tts-prs

codex/depot-runners

chore/migrate-selected-plugins-to-uv-lock

fix/repair-failed-plugin-deploys

ci/fix-plugin-change-detection

chore/migrate-aws-s3-storage-to-uv-lock

chore/migrate-somark-dependencies-to-uv-lock

ci/uv-lock-dependency-validation

fix/2911-openai-api-compatible-tool-call-content

chore/remove-deprecated-plugins

copilot/add-more-models-openrouter-provider

copilot/fix-error-connecting-fireworks-ai

fix/openai-compatible-max-completion-tokens-validation

fix/gemini-lockfile

chore/add-React-fallback-desc

feat/add-gemini-embedding-2-preview

copilot/add-claude-sonnet-opus-4-6

codex/update-xai-models-2721

fix/remove-sentence-transformer-for-hubspot

feat/add-gpt-5.4

copilot/fix-ci-errors-and-bump-version

copilot/fix-security-errors-combined

copilot/update-gemini-model-version

fix/anthropic-parallel-tool-call

codex/fix-azure-ai-studio-azure-core-1-38

codex/fix-azure-blob-azure-core-1-38

codex/fix-azure-openai-azure-core-1-38

gitlab-credentials-c

fix/openrouter-validation-model

fix/gemini-null-checks

fix/deepseek-tool-message-ignore

fix/gemini-dependencies

No results found.

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

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#907