dify - 💡(How to fix) Fix Output node retains legacy "End" node restrictions after rename [1 comments, 2 participants]

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.13.3

Cloud or Self Hosted

Cloud

Steps to reproduce

The Output node (formerly "End") was redesigned: it is no longer required, Output Variable is now mandatory, and it can be inserted mid-workflow to surface data without stopping execution. However, several frontend behaviors still assume the old "terminal End node" semantics.

Issue 1: Cannot add nodes after an Output node

1. Create a workflow: User Input → LLM.
2. Add an Output node after the LLM node.
3. Try to add another node after the Output node.

You cannot — the Output node blocks all downstream connections. Inserting an Output node between two existing connected nodes (via "Add Node" on an edge) works fine, but adding one at the end of a branch makes it a dead end.

This is because use-available-blocks.ts still treats BlockEnum.End as a terminal node and returns an empty availableNextBlocks array.

Issue 2: No visual separator between outputs from multiple Output nodes

1. Create a workflow: User Input → LLM → Output → LLM 2 → Output 2 (insert the first Output node between LLM and LLM 2).
2. Configure each Output node to reference its upstream LLM's text output.
3. Run the workflow in the WebApp.

The two outputs are concatenated into a single text block with no spacing or delimiter between them. It is very difficult to tell where one output ends and the next begins.

Issue 3: Duplicate variable names across Output nodes silently overwrite

1. Using the same workflow as Issue 2, note that both Output nodes default their variable name to text (since they both reference an LLM's text output).
2. Run the workflow.

The WebApp only shows the result from the last Output node to execute. The first output is silently overwritten because both share the variable name text. There is no validation or warning preventing duplicate names across different Output nodes.

✔️ Expected Behavior

1. Users should be able to add nodes after an Output node, since it no longer serves as a workflow terminator.
2. When multiple Output nodes execute, their results should be visually separated in the WebApp.
3. The frontend should either prevent duplicate variable names across Output nodes, or warn the user that values will be overwritten.

Additionally: since Output Variable is now a required field, the Output node panel should initialize with one empty variable row by default, rather than requiring the user to manually click + first.

❌ Actual Behavior

1. Output node blocks all downstream connections (legacy End node behavior in use-available-blocks.ts).
2. Multiple outputs concatenate into raw unseparated text.
3. Duplicate variable names across Output nodes cause silent overwrite with no warning.