See every workflow run
as it happens, end to end

The live status surface shows every currently running workflow with its real time state: which step is executing right now, how far the run has progressed, how long it has been running, and a health indicator that flags anything unhealthy. The view auto refreshes as steps complete, so the team always sees the freshest picture without refreshing the page. Filter by workflow, status, or trigger source to focus on the executions that matter.

Every step produces a structured log entry with full context: the step name and node type, the inputs received, the outputs produced, the start and end timestamps, the duration, the status (success, failure, retried), any retries with their outcomes, and any inline notes the workflow logged. The entries are arranged top to bottom in execution order, so reading the log feels like reading a narrative of the run rather than piecing it together.

When a step fails, the error appears in the log with complete diagnostic context: the message returned by the failing operation, the underlying cause when there is a deeper error chain, the inputs being processed when it failed, the exact step and line, and the full stack trace when available. For errors from external services, the response body and status are captured too. The whole panel expands inline, so there is no need to leave the run.

The visual timeline shows every step as a horizontal bar sized to its actual duration, arranged in execution order. Slow steps appear as long bars next to short ones, making the bottleneck immediately visible without reading a list of timestamps. Parallel branches show side by side so simultaneous work is easy to see. Retries and waits appear as distinct segments, so you can tell productive work from backoff. Hover any segment for the exact timing.

Execution history is retained for the lifetime of the workspace by default, so every run is searchable and replayable for as long as the workspace exists. Configurable retention policies are available for teams who prefer to age out older runs after a set window, with automatic export to long term storage before deletion so the audit trail stays available. The retention setting is configured per workflow, so high frequency workflows can have shorter windows than critical ones.

Yes, execution events can drive notifications and alerts through the same channels the team already uses: email, Slack, Microsoft Teams, custom webhook destinations, and the WorksBuddy notification center. Rules can fire on conditions such as a workflow failing, a workflow taking longer than expected, an error rate exceeding a threshold, or a step pattern repeating. The team gets the right alert at the right time without wiring up a separate monitoring product.