Feature Request: Error Nodes for Workflows

What's the idea? Add a dedicated "Error Node" to the Workflow builder — a node you can place on any branch to explicitly halt a workflow and mark it as failed, rather than letting it run into an empty dead-end branch that gets marked as successful. --- Why would this be useful? Right now, if a workflow hits a condition that isn't met, the execution just runs into an empty branch — and still gets marked as successful. There's no way to communicate to the person who triggered it that something was actually wrong or incomplete. An Error Node would let workflow builders add intentional failure paths with a clear, human-readable explanation, making workflows much more self-sufficient and user-friendly. --- What could it look like? At its simplest, an Error Node just emits an error state — halting the workflow and marking the run as failed in the execution history. That alone would already be a big improvement over the current silent dead-end be…