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

Error retrieving the next question #20536

New Issue
Closed
opened 2026-02-21 20:07:52 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:07:52 -05:00
Owner
Copy Link
Copy Source

Originally created by @hangshao009 on GitHub (Nov 25, 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

1.9.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I updated from 1.1.3 to 1.9.1, I performed the following merge.
Image
However, when I was using the big model for the conversation, an error occurred. After troubleshooting, it was found that an error occurred when obtaining the next question. The error is as follows:
Image
ValueError: Model qwen3-30b-a3b-Instruct-2507 is disabled, but I did not use this model here. I'm not sure if it's a plugin issue.

✔️ Expected Behavior

no issue

❌ Actual Behavior

issue,no next question

Originally created by @hangshao009 on GitHub (Nov 25, 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 1.9.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When I updated from 1.1.3 to 1.9.1, I performed the following merge. <img width="1018" height="605" alt="Image" src="https://github.com/user-attachments/assets/65ee663f-9cba-4b28-9f28-945b263e963f" /> However, when I was using the big model for the conversation, an error occurred. After troubleshooting, it was found that an error occurred when obtaining the next question. The error is as follows: <img width="1671" height="867" alt="Image" src="https://github.com/user-attachments/assets/6988924d-80fd-4695-a84e-0baaa4b034eb" /> ValueError: Model qwen3-30b-a3b-Instruct-2507 is disabled, but I did not use this model here. I'm not sure if it's a plugin issue. ### ✔️ Expected Behavior no issue ### ❌ Actual Behavior issue,no next question
yindo added the 🐞 bug label 2026-02-21 20:07:52 -05:00
yindo closed this issue 2026-02-21 20:07:52 -05:00
yindo commented 2026-02-21 20:07:52 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 25, 2025):

The error happens because Dify is trying to use the model qwen3-30b-a3b-Instruct-2507, but it is marked as disabled in your configuration. This can occur after an upgrade if model settings or plugin configs are lost or reset, or if the suggestion/question generator is defaulting to a disabled model—even if your main conversation uses a different one.

To fix this:

  1. Check and re-enable the model: In the Dify admin UI (or via the /workspaces/current/model-providers/<provider>/models/enable API endpoint), verify if qwen3-30b-a3b-Instruct-2507 is disabled for your provider and model type. If so, re-enable it. This updates the ProviderModelSetting table and allows the model to be used again in workflows and suggestion generation.
    Reference

  2. Check YAML configuration: Make sure the YAML file for this model exists in the correct directory (usually /app/storage/cwd/langgenius/tongyi-*/models/llm inside the plugin daemon container), is readable, and includes all required fields like description. Missing or malformed YAMLs can cause the model to be marked as disabled.
    Reference

  3. Plugin and environment: Ensure your Tongyi/Qwen plugin is at least version 0.0.19, and that you have restarted the plugin daemon container after any changes to YAMLs, volumes, or environment variables. Double-check that your Docker volume mounts and environment variables (like PLUGIN_DAEMON_URL, SANDBOX_ENABLE_NETWORK, PLUGIN_WORKING_PATH, and PLUGIN_STORAGE_LOCAL_ROOT) are set correctly so the plugin daemon can access the model files.
    Reference

  4. Default model selection: If the error persists, check which model is set as the default for suggestion/question generation in your workspace. If the default is a disabled model, update it to an enabled one using the admin UI or the /workspaces/current/default-model API.
    Reference

  5. Logs and cache: If you still see the error, review the plugin daemon and Dify logs for clues, and consider clearing plugin/model caches or database entries related to model settings.

This issue is common after upgrades if model configs are lost or if the plugin system changes how defaults are selected. Re-enabling the model and ensuring all configs and files are correct should resolve it.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 25, 2025): <!-- Answer --> The error happens because Dify is trying to use the model `qwen3-30b-a3b-Instruct-2507`, but it is marked as disabled in your configuration. This can occur after an upgrade if model settings or plugin configs are lost or reset, or if the suggestion/question generator is defaulting to a disabled model—even if your main conversation uses a different one. To fix this: 1. **Check and re-enable the model:** In the Dify admin UI (or via the `/workspaces/current/model-providers/<provider>/models/enable` API endpoint), verify if `qwen3-30b-a3b-Instruct-2507` is disabled for your provider and model type. If so, re-enable it. This updates the `ProviderModelSetting` table and allows the model to be used again in workflows and suggestion generation. [Reference](https://github.com/langgenius/dify/blob/57b405c4c2724b63be8b82525a23c1575db26aef/api/controllers/console/workspace/models.py#L31-L477) 2. **Check YAML configuration:** Make sure the YAML file for this model exists in the correct directory (usually `/app/storage/cwd/langgenius/tongyi-*/models/llm` inside the plugin daemon container), is readable, and includes all required fields like `description`. Missing or malformed YAMLs can cause the model to be marked as disabled. [Reference](https://github.com/langgenius/dify-official-plugins/issues/1110#issuecomment-2982528354) 3. **Plugin and environment:** Ensure your Tongyi/Qwen plugin is at least version 0.0.19, and that you have restarted the plugin daemon container after any changes to YAMLs, volumes, or environment variables. Double-check that your Docker volume mounts and environment variables (like `PLUGIN_DAEMON_URL`, `SANDBOX_ENABLE_NETWORK`, `PLUGIN_WORKING_PATH`, and `PLUGIN_STORAGE_LOCAL_ROOT`) are set correctly so the plugin daemon can access the model files. [Reference](https://github.com/langgenius/dify/blob/57b405c4c2724b63be8b82525a23c1575db26aef/docker/docker-compose.yaml#L467-L934) 4. **Default model selection:** If the error persists, check which model is set as the default for suggestion/question generation in your workspace. If the default is a disabled model, update it to an enabled one using the admin UI or the `/workspaces/current/default-model` API. [Reference](https://github.com/langgenius/dify/blob/57b405c4c2724b63be8b82525a23c1575db26aef/api/controllers/console/workspace/models.py#L31-L477) 5. **Logs and cache:** If you still see the error, review the plugin daemon and Dify logs for clues, and consider clearing plugin/model caches or database entries related to model settings. This issue is common after upgrades if model configs are lost or if the plugin system changes how defaults are selected. Re-enabling the model and ensuring all configs and files are correct should resolve it. <!-- 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/f715d62c-2bbf-4f51-840f-8c16251ad4b8?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f715d62c-2bbf-4f51-840f-8c16251ad4b8?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f715d62c-2bbf-4f51-840f-8c16251ad4b8?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f715d62c-2bbf-4f51-840f-8c16251ad4b8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f715d62c-2bbf-4f51-840f-8c16251ad4b8?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f715d62c-2bbf-4f51-840f-8c16251ad4b8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f715d62c-2bbf-4f51-840f-8c16251ad4b8?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20error%20happens%20because%20Dify%20is%20trying%20to%20use%20the%20model%20%60qwen3-30b-a3b-Instruct-2507%60%2C%20but%20it%20is%20marked%20as%20disabled%20in%20your%20configuration.%20This%20can%20occur%20after%20an%20upgrade%20if%20model%20settings%20or%20plugin%20configs%20are%20lost%20or%20reset%2C%20or%20if%20the%20suggestion/question%20generator%20is%20defaulting%20to%20a%20disabled%20model%E2%80%94even%20if%20your%20main%20conversation%20uses%20a%20different%20one.%0A%0ATo%20fix%20this%3A%0A%0A1.%20%2A%2ACheck%20and%20re-enable%20the%20model%3A%2A%2A%20In%20the%20Dify%20admin%20UI%20%28or%20via%20the%20%60/workspaces/current/model-providers/%3Cprovider%3E/models/enable%60%20API%20endpoint%29%2C%20verify%20if%20%60qwen3-30b-a3b-Instruct-2507%60%20is%20disabled%20for%20your%20provider%20and%20model%20type.%20If%20so%2C%20re-enable%20it.%20This%20updates%20the%20%60ProviderModelSetting%60%20table%20and%20allows%20the%20model%20to%20be%20used%20again%20in%20workflows%20and%20suggestion%20generation.%20%20%0A%20%20%20%5BReference%5D%28https%3A//github.com/langgenius/dify/blob/57b405c4c2724b63be8b82525a23c1575db26aef/api/controllers/console/workspace/models.py%23L31-L477%29%0A%0A2.%20%2A%2ACheck%20YAML%20configuration%3A%2A%2A%20Make%20sure%20the%20YAML%20file%20for%20this%20model%20exists%20in%20the%20correct%20directory%20%28usually%20%60/app/storage/cwd/langgenius/tongyi-%2A/models/llm%60%20inside%20the%20plugin%20daemon%20container%29%2C%20is%20readable%2C%20and%20includes%20all%20required%20fields%20like%20%60description%60.%20Missing%20or%20malformed%20YAMLs%20can%20cause%20the%20model%20to%20be%20marked%20as%20disabled.%20%20%0A%20%20%20%5BReference%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1110%23issuecomment-2982528354%29%0A%0A3.%20%2A%2APlugin%20and%20environment%3A%2A%2A%20Ensure%20your%20Tongyi/Qwen%20plugin%20is%20at%20least%20version%200.0.19%2C%20and%20that%20you%20have%20restarted%20the%20plugin%20daemon%20container%20after%20any%20changes%20to%20YAMLs%2C%20volumes%2C%20or%20environment%20variables.%20Double-check%20that%20your%20Docker%20volume%20mounts%20and%20environment%20variables%20%28like%20%60PLUGIN_DAEMON_URL%60%2C%20%60SANDBOX_ENABLE_NETWORK%60%2C%20%60PLUGIN_WORKING_PATH%60%2C%20and%20%60PLUGIN_STORAGE_LOCAL_ROOT%60%29%20are%20set%20correctly%20so%20the%20plugin%20daemon%20can%20access%20the%20model%20files.%20%20%0A%20%20%20%5BReference%5D%28https%3A//github.com/langgenius/dify/blob/57b405c4c2724b63be8b82525a23c1575db26aef/docker/docker-compose.yaml%23L467-L934%29%0A%0A4.%20%2A%2ADefault%20model%20selection%3A%2A%2A%20If%20the%20error%20persists%2C%20check%20which%20model%20is%20set%20as%20the%20default%20for%20suggestion/question%20generation%20in%20your%20workspace.%20If%20the%20default%20is%20a%20disabled%20model%2C%20update%20it%20to%20an%20enabled%20one%20using%20the%20admin%20UI%20or%20the%20%60/workspaces/current/default-model%60%20API.%20%20%0A%20%20%20%5BReference%5D%28https%3A//github.com/langgenius/dify/blob/57b405c4c2724b63be8b82525a23c1575db26aef/api/controllers/console/workspace/models.py%23L31-L477%29%0A%0A5.%20%2A%2ALogs%20and%20cache%3A%2A%2A%20If%20you%20still%20see%20the%20error%2C%20review%20the%20plugin%20daemon%20and%20Dify%20logs%20for%20clues%2C%20and%20consider%20clearing%20plugin/model%20caches%20or%20database%20entries%20related%20to%20model%20settings.%0A%0AThis%20issue%20is%20common%20after%20upgrades%20if%20model%20configs%20are%20lost%20or%20if%20the%20plugin%20system%20changes%20how%20defaults%20are%20selected.%20Re-enabling%20the%20model%20and%20ensuring%20all%20configs%20and%20files%20are%20correct%20should%20resolve%20it.)&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/28634)
yindo commented 2026-02-21 20:07:52 -05:00
Author
Owner
Copy Link
Copy Source

@hangshao009 commented on GitHub (Nov 25, 2025):

thanks i fix it

@hangshao009 commented on GitHub (Nov 25, 2025): thanks i fix it
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#20536
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?