@horw Hello! I'm here to assist you with any bugs, questions, or contributions you have. I'm Dosu, a bot designed to help you while waiting for a human maintainer.

The issue you're experiencing with the 'NEXT STEP' feature not adding connections in the Dify workflow could be related to several constraints or conditions that prevent the addition of new blocks. Here are some potential reasons:

1. Parallel Limit Check: If the checkParallelLimit function returns false for the given node, it will prevent the block selector from opening, thus not allowing new connections to be added ^[1].

2. Read-Only Mode: If the workflow is in a read-only state (nodesReadOnly is true), the block selector will be disabled, preventing any new blocks from being added ^[1].

3. Node Compatibility: The getAvailableNextNodes function might return an empty array for the specific block type, indicating that no subsequent nodes are allowed for that block type. This is defined in the NODES_EXTRA_DATA configuration ^[2].

4. Maximum Tree Depth: There might be a maximum limit of nodes per branch, which can prevent adding new blocks if the limit is reached ^[2].

5. Workflow Requirements: Certain blocks like the 'End' block must be added according to workflow constraints, which might restrict the addition of other blocks if these requirements are not met ^[2].

These constraints could be affecting the 'NEXT STEP' feature in your workflow. You might want to check these conditions in your setup to see if any of them apply.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}