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

Workflows are forced to output something #20455

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

Originally created by @DavideDelbianco on GitHub (Nov 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.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Have a workflow that is meant to be triggered by API call.

✔️ Expected Behavior

Pre 1.10.0 it could end without returning.

❌ Actual Behavior

The workflow is forced to return something:

Image
Originally created by @DavideDelbianco on GitHub (Nov 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.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Have a workflow that is meant to be triggered by API call. ### ✔️ Expected Behavior Pre 1.10.0 it could end without returning. ### ❌ Actual Behavior The workflow is forced to return something: <img width="957" height="572" alt="Image" src="https://github.com/user-attachments/assets/c458f8d2-dbf3-47cd-8c7e-e15effe85e4c" />
yindo added the 🌊 feat:workflow label 2026-02-21 20:07:31 -05:00
yindo closed this issue 2026-02-21 20:07:31 -05:00
yindo commented 2026-02-21 20:07:31 -05:00
Author
Owner
Copy Link
Copy Source

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

In Dify 1.10.0, workflows triggered by API calls are now required to return an output, even if it's just an empty object. This is enforced by the backend: the workflow execution always produces a finish response with an outputs field, which defaults to {} if no node writes an output. There is no configuration or documented workaround to allow workflows to end without returning a value—the framework expects a response for every workflow run, and this behavior appears to be intentional for consistency and API contract reasons. If you need to signal "no output," you can design your workflow to return an empty object or a specific value indicating that state, but omitting the output entirely is not supported in the current version.
You can review the relevant implementation in the workflow response converter and pipeline logic for more details:
Workflow response converter
Workflow pipeline

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 (Nov 20, 2025): <!-- Answer --> In Dify 1.10.0, workflows triggered by API calls are now required to return an output, even if it's just an empty object. This is enforced by the backend: the workflow execution always produces a finish response with an `outputs` field, which defaults to `{}` if no node writes an output. There is no configuration or documented workaround to allow workflows to end without returning a value—the framework expects a response for every workflow run, and this behavior appears to be intentional for consistency and API contract reasons. If you need to signal "no output," you can design your workflow to return an empty object or a specific value indicating that state, but omitting the output entirely is not supported in the current version. You can review the relevant implementation in the workflow response converter and pipeline logic for more details: [Workflow response converter](https://github.com/langgenius/dify/blob/d1c9183d3b14335097b78ebabbc57ddf94c8e1e2/api/core/app/apps/common/workflow_response_converter.py#L73-L678) [Workflow pipeline](https://github.com/langgenius/dify/blob/d1c9183d3b14335097b78ebabbc57ddf94c8e1e2/api/core/app/apps/workflow/generate_task_pipeline.py#L67-L631) <!-- 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/314c1368-12e0-4020-a2a7-3c6aa40b81d5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/314c1368-12e0-4020-a2a7-3c6aa40b81d5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/314c1368-12e0-4020-a2a7-3c6aa40b81d5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/314c1368-12e0-4020-a2a7-3c6aa40b81d5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/314c1368-12e0-4020-a2a7-3c6aa40b81d5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/314c1368-12e0-4020-a2a7-3c6aa40b81d5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/314c1368-12e0-4020-a2a7-3c6aa40b81d5?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/28474)
yindo commented 2026-02-21 20:07:31 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Nov 21, 2025):

@dosu
The workflow was an old one, and retained the old node name "End".
Now the node is called "Output" and you use it only if you want to output something.

The workflow does not have to output something at all and the node is no longer mandatory.

@DavideDelbianco commented on GitHub (Nov 21, 2025): @dosu The workflow was an old one, and retained the old node name "End". Now the node is called "Output" and you use it only if you want to output something. The workflow does not have to output something at all and the node is no longer mandatory.
yindo commented 2026-02-21 20:07:31 -05:00
Author
Owner
Copy Link
Copy Source

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

You're correct—the 'Output' node (previously 'End') is now optional in Dify 1.10.0. You only need to use it if you want to output something; workflows can end without producing any output, and the node is no longer mandatory. This is supported by both the backend logic and recent updates: the workflow engine simply collects outputs if present, but will complete and return an empty output if none are set, and validation rules do not require an Output node for workflow completion (source, source, source). Legacy workflows with the old 'End' node still work, but it's no longer required. Let me know if you want details on edge cases or migration!

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 (Nov 21, 2025): <!-- Answer --> You're correct—the 'Output' node (previously 'End') is now optional in Dify 1.10.0. You only need to use it if you want to output something; workflows can end without producing any output, and the node is no longer mandatory. This is supported by both the backend logic and recent updates: the workflow engine simply collects outputs if present, but will complete and return an empty output if none are set, and validation rules do not require an Output node for workflow completion ([source](https://github.com/langgenius/dify/blob/2e0964e0b066cadee3b1b75ab5a5bf2e5f1d2379/api/core/app/apps/common/workflow_response_converter.py#L73-L678), [source](https://github.com/langgenius/dify/issues/22093#issuecomment-3163108397), [source](https://github.com/langgenius/dify/pull/28012)). Legacy workflows with the old 'End' node still work, but it's no longer required. Let me know if you want details on edge cases or migration! <!-- 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/06a88350-0550-4053-86e4-af3e854162ad?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/06a88350-0550-4053-86e4-af3e854162ad?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/06a88350-0550-4053-86e4-af3e854162ad?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/06a88350-0550-4053-86e4-af3e854162ad?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/06a88350-0550-4053-86e4-af3e854162ad?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/06a88350-0550-4053-86e4-af3e854162ad?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/06a88350-0550-4053-86e4-af3e854162ad?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/28474)
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 🌊 feat:workflow
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#20455
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?