Calling qwen3:30b, the thinking process is the thinking field, but there is no thinking field in dify #736

Closed
opened 2026-02-16 10:20:20 -05:00 by yindo · 5 comments
Owner

Originally created by @FallenAngels520 on GitHub (Oct 20, 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

Calling qwen3:30b:

Image

in dify:

Image there is no thinking field also no

✔️ Expected Behavior

Calling qwen3:30b, the thinking process is the thinking field, but there is no thinking field in dify

Actual Behavior

Calling qwen3:30b:

Image

in dify:

Image
Originally created by @FallenAngels520 on GitHub (Oct 20, 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 Calling qwen3:30b: <img width="1505" height="580" alt="Image" src="https://github.com/user-attachments/assets/a5b7ebaf-2131-4991-af34-bed471582289" /> in dify: <img width="691" height="831" alt="Image" src="https://github.com/user-attachments/assets/57a1e8c4-15bc-4f48-9d81-69d40fe5bb40" /> there is no thinking field also no <think></think> ### ✔️ Expected Behavior Calling qwen3:30b, the thinking process is the thinking field, but there is no thinking field in dify ### ❌ Actual Behavior Calling qwen3:30b: <img width="1505" height="580" alt="Image" src="https://github.com/user-attachments/assets/ac534d46-c379-4de0-958b-abaacfaf9e30" /> in dify: <img width="691" height="831" alt="Image" src="https://github.com/user-attachments/assets/57a1e8c4-15bc-4f48-9d81-69d40fe5bb40" />
yindo added the bug label 2026-02-16 10:20:20 -05:00
yindo closed this issue 2026-02-16 10:20:20 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Oct 20, 2025):

Dify does have logic to extract and handle tags (the "thinking" field) from LLM outputs, but this only works if the model's response actually includes those tags. The handling depends on the reasoning_format setting: if set to "separated", Dify will extract the content inside tags and expose it as a separate reasoning_content field; if set to "tagged", it keeps the tags in the main text for backward compatibility. If the qwen3:30b model (or its integration via Ollama) does not output tags, or if the workflow node's reasoning_format is not set appropriately, you won't see a "thinking" field in the output. There is currently no UI component in Dify that displays a "thinking" process indicator unless the model and configuration both support and emit it.

If you want to surface the "thinking" field, ensure your prompt and model are configured to output tags, and set the node's reasoning_format to "separated" in your workflow configuration. Otherwise, Dify will not display this field, and this is expected behavior given the current implementation.

Reference: LLMNode reasoning handling in Dify

To reply, just mention @dosu.


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

@dosubot[bot] commented on GitHub (Oct 20, 2025): <!-- Answer --> Dify does have logic to extract and handle <think></think> tags (the "thinking" field) from LLM outputs, but this only works if the model's response actually includes those tags. The handling depends on the `reasoning_format` setting: if set to "separated", Dify will extract the content inside <think> tags and expose it as a separate `reasoning_content` field; if set to "tagged", it keeps the tags in the main text for backward compatibility. If the qwen3:30b model (or its integration via Ollama) does not output <think> tags, or if the workflow node's `reasoning_format` is not set appropriately, you won't see a "thinking" field in the output. There is currently no UI component in Dify that displays a "thinking" process indicator unless the model and configuration both support and emit it. If you want to surface the "thinking" field, ensure your prompt and model are configured to output <think> tags, and set the node's `reasoning_format` to "separated" in your workflow configuration. Otherwise, Dify will not display this field, and this is expected behavior given the current implementation. Reference: [LLMNode reasoning handling in Dify](https://github.com/langgenius/dify/blob/d7d9abb007f136fd10e823fee20cf9e15b972b0d/api/core/workflow/nodes/llm/node.py) <!-- 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/2f1c3e56-1f9d-47e0-b299-2ffb2e8b56fe?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2f1c3e56-1f9d-47e0-b299-2ffb2e8b56fe?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2f1c3e56-1f9d-47e0-b299-2ffb2e8b56fe?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2f1c3e56-1f9d-47e0-b299-2ffb2e8b56fe?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2f1c3e56-1f9d-47e0-b299-2ffb2e8b56fe?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2f1c3e56-1f9d-47e0-b299-2ffb2e8b56fe?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2f1c3e56-1f9d-47e0-b299-2ffb2e8b56fe?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/27149)
Author
Owner

@crazywoola commented on GitHub (Oct 20, 2025):

Issues related to plugins should use this template https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml

@crazywoola commented on GitHub (Oct 20, 2025): Issues related to plugins should use this template [https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml](https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml)
Author
Owner

@dosubot[bot] commented on GitHub (Oct 20, 2025):

The 'thinking' field or indicator is not shown in Dify for qwen3:30b because Dify's UI and backend only display these indicators when the model response includes explicit intermediate reasoning or streaming updates. For qwen3:30b via the ollama provider, there is no default support for a 'thinking' field or tag in the output, and Dify does not add this field unless the model or integration provides it. The frontend relies on agent thoughts, workflow process data, or streaming token updates to show intermediate states, but if the backend only returns completed text, the 'thinking' UI will not trigger. Recent updates have improved handling of structured output and streaming, but unless the model response includes the necessary markers, the 'thinking' field will remain absent in the UI. If you need this feature, check if your model or provider can emit tags or intermediate reasoning, and ensure Dify is configured for streaming mode where possible.

For more details, see the relevant frontend logic here and recent backend streaming/structured output improvements here.

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 (Oct 20, 2025): <!-- Answer --> The 'thinking' field or <think></think> indicator is not shown in Dify for qwen3:30b because Dify's UI and backend only display these indicators when the model response includes explicit intermediate reasoning or streaming updates. For qwen3:30b via the ollama provider, there is no default support for a 'thinking' field or <think></think> tag in the output, and Dify does not add this field unless the model or integration provides it. The frontend relies on agent thoughts, workflow process data, or streaming token updates to show intermediate states, but if the backend only returns completed text, the 'thinking' UI will not trigger. Recent updates have improved handling of structured output and streaming, but unless the model response includes the necessary markers, the 'thinking' field will remain absent in the UI. If you need this feature, check if your model or provider can emit <think></think> tags or intermediate reasoning, and ensure Dify is configured for streaming mode where possible. For more details, see the relevant frontend logic [here](https://github.com/langgenius/dify/blob/d7d9abb007f136fd10e823fee20cf9e15b972b0d/web/app/components/base/chat/chat/answer/index.tsx) and recent backend streaming/structured output improvements [here](https://github.com/langgenius/dify/pull/27089). <!-- 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/ca70a159-4251-42cb-9af5-5147d5c1ce63?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ca70a159-4251-42cb-9af5-5147d5c1ce63?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ca70a159-4251-42cb-9af5-5147d5c1ce63?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ca70a159-4251-42cb-9af5-5147d5c1ce63?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ca70a159-4251-42cb-9af5-5147d5c1ce63?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ca70a159-4251-42cb-9af5-5147d5c1ce63?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ca70a159-4251-42cb-9af5-5147d5c1ce63?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-official-plugins/issues/1898)
Author
Owner

@FallenAngels520 commented on GitHub (Oct 20, 2025):

@dosu qwen3:30b is a reasoning model. The thinking process is not spliced ​​into the content, but is represented by a separate thinking field. However, in dify, only the content field is obtained and the thinking field is discarded. Therefore, the thinking process will not be displayed in dify.

As shown in the figure:

Image
@FallenAngels520 commented on GitHub (Oct 20, 2025): [@dosu](https://go.dosu.dev/dosubot) qwen3:30b is a reasoning model. The thinking process is not spliced ​​into the content, but is represented by a separate thinking field. However, in dify, only the content field is obtained and the thinking field is discarded. Therefore, the thinking process will not be displayed in dify. As shown in the figure: <img width="663" height="797" alt="Image" src="https://github.com/user-attachments/assets/defde180-12eb-41be-91a3-1e79caa15db9" />
Author
Owner

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

Hi, @FallenAngels520. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that the "thinking" field for the qwen3:30b reasoning model in Dify v1.9.1 is missing, showing only the content field.
  • The "thinking" field appears only if the model outputs tags and the workflow's reasoning_format is set correctly.
  • qwen3:30b via Ollama does not emit these tags by default, so Dify's UI does not show intermediate reasoning.
  • You confirmed that Dify discards the separate thinking field despite the model providing it.
  • The resolution involves adjusting the model and configuration to output the required tags and set reasoning_format to enable the "thinking" field display.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of dify-official-plugins, and if so, you can keep the discussion open by commenting here.
  • Otherwise, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 6, 2025): Hi, @FallenAngels520. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that the "thinking" field for the qwen3:30b reasoning model in Dify v1.9.1 is missing, showing only the content field. - The "thinking" field appears only if the model outputs <think></think> tags and the workflow's reasoning_format is set correctly. - qwen3:30b via Ollama does not emit these tags by default, so Dify's UI does not show intermediate reasoning. - You confirmed that Dify discards the separate thinking field despite the model providing it. - The resolution involves adjusting the model and configuration to output the required tags and set reasoning_format to enable the "thinking" field display. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of dify-official-plugins, and if so, you can keep the discussion open by commenting here. - Otherwise, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#736