Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?
SaaS
What are the exact steps to reproduce this issue?
Workspace / Location:
• Database: “Connected Systems Platform” (id 530172)
• Automation app: “Package Health Recalculation” (id 532203)
• Workflow: id 53683, “Status is updated in Date Change Requests” trigger
Summary:
A Router node (UI label “Follow 1 of 2 branches”) does not restrict execution to the matched branch. Every trigger firing runs the downstream nodes of both the matched conditional edge and the default edge, even though the router’s own dispatch step (visible in the run’s History payload) reflects only one matched edge. Based on the documented contract — CoreRouterService.dispatch_data returns a single output_uid, and AutomationNodeHandler.get_next_nodes is meant to filter a node’s children to those whose previous_node_output equals that output_uid — this looks like the runner may be invoking get_next_nodes without passing the dispatched output_uid (e.g. passing None), which would skip that filter and return all children of the router regardless of which edge matched.
Rou