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

Boolean type variable (from structured output) doesn't work in IF/ELSE node #19987

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

Originally created by @fniu on GitHub (Oct 28, 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.2

Cloud or Self Hosted

Cloud

Steps to reproduce

When a Boolean variable is used as a condition in a IF/ELSE node, it is not treated as a Boolean variable, and it is impossible to the "true" branch. See below, when such as a variable is used, it doesn't show "True" or "False" options.

Image Image

✔️ Expected Behavior

The boolean variable is treated as a Boolean

❌ Actual Behavior

The node asks user to fill in a value, and it will never make the condition true.

Originally created by @fniu on GitHub (Oct 28, 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.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce When a Boolean variable is used as a condition in a IF/ELSE node, it is not treated as a Boolean variable, and it is impossible to the "true" branch. See below, when such as a variable is used, it doesn't show "True" or "False" options. <img width="716" height="103" alt="Image" src="https://github.com/user-attachments/assets/72eb536f-4ea0-4369-a567-eb66a16a182c" /> <img width="1148" height="297" alt="Image" src="https://github.com/user-attachments/assets/65533fb0-0d6d-49b3-9c4d-c5efa1351005" /> ### ✔️ Expected Behavior The boolean variable is treated as a Boolean ### ❌ Actual Behavior The node asks user to fill in a value, and it will never make the condition true.
yindo added the 🐞 bug label 2026-02-21 20:05:16 -05:00
yindo closed this issue 2026-02-21 20:05:16 -05:00
yindo commented 2026-02-21 20:05:16 -05:00
Author
Owner
Copy Link
Copy Source

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

This is a known bug in Dify 1.9.2: Boolean variables from structured outputs aren't recognized as Boolean in IF/ELSE nodes, so the UI doesn't show True/False options and the condition can't be evaluated as expected. The backend supports Boolean types correctly, but the frontend fails to infer the type for nested fields, causing this issue.

Recent merged pull requests have improved type handling and condition evaluation for workflow nodes, including IF/ELSE nodes and Boolean variables. If you're on the cloud version, these fixes may already be live or will be soon. Updating to the latest version should resolve the problem (PR #27009, PR #27051).

If you need a workaround before the fix is available, you could try mapping your Boolean to a string or integer in a previous node, then check that value in your IF/ELSE node. This isn't ideal, but it can unblock your workflow until the Boolean type is properly supported in the UI.

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 28, 2025): <!-- Answer --> This is a known bug in Dify 1.9.2: Boolean variables from structured outputs aren't recognized as Boolean in IF/ELSE nodes, so the UI doesn't show True/False options and the condition can't be evaluated as expected. The backend supports Boolean types correctly, but the frontend fails to infer the type for nested fields, causing this issue. Recent merged pull requests have improved type handling and condition evaluation for workflow nodes, including IF/ELSE nodes and Boolean variables. If you're on the cloud version, these fixes may already be live or will be soon. Updating to the latest version should resolve the problem ([PR #27009](https://github.com/langgenius/dify/pull/27009), [PR #27051](https://github.com/langgenius/dify/pull/27051)). If you need a workaround before the fix is available, you could try mapping your Boolean to a string or integer in a previous node, then check that value in your IF/ELSE node. This isn't ideal, but it can unblock your workflow until the Boolean type is properly supported in the UI. <!-- 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/9537b156-ecc4-4260-b872-ddebd8b5f036?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9537b156-ecc4-4260-b872-ddebd8b5f036?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9537b156-ecc4-4260-b872-ddebd8b5f036?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9537b156-ecc4-4260-b872-ddebd8b5f036?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9537b156-ecc4-4260-b872-ddebd8b5f036?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9537b156-ecc4-4260-b872-ddebd8b5f036?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9537b156-ecc4-4260-b872-ddebd8b5f036?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/27568)
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#19987
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?