Portal Community

Filter Chips

All
Running
Failed
Suspended
Completed
Skipped
Pending

Filter Behaviour

FilterShowsUse Case
All (default)Every node regardless of statusSee the full execution overview
RunningOnly nodes currently executingWatch active progress during long executions
FailedOnly nodes that failed — includes nodes that failed but were retried successfully (no)Quick failure diagnosis
SuspendedNodes awaiting HIL inputSee which nodes need human action
CompletedNodes that finished (includes skipped)Verify expected nodes ran
SkippedOnly nodes bypassed by conditional logicVerify branching worked correctly
PendingNodes not yet reachedPreview remaining work

Multi-Status Filter

Multiple chips can be active simultaneously. For example, selecting "Failed" and "Running" shows all nodes that are currently in a problematic or in-progress state:

// Filter applied as: show node if its status is in selectedStatuses
const visibleNodes = allNodes.filter(node =>
  selectedStatuses.size === 0          // "All" selected
  || selectedStatuses.has(node.status) // specific statuses selected
);
Filter Persists During Execution The filter stays active while the execution runs. As new events arrive and node statuses change, the visible list updates dynamically to match the current filter. A node that transitions from Running to Completed will disappear from the "Running" filter view immediately.