Error Display — Execution Status Tab

Error Panel — Visual Example

Execution Failed

HttpRequestException

The HTTP request to https://api.example.com/invoices timed out after 30 seconds. Node: http-request-1.

Show stack trace

System.Net.Http.HttpRequestException: Request timeout after 30000ms
at BizFirst.ExecutionNodes.HttpRequest.HttpRequestExecutor.ExecuteInternalAsync()
at BizFirst.ProcessEngine.BaseNodeExecutor.ExecuteAsync()
at BizFirst.ProcessEngine.WorkflowRunner.RunNodeAsync()

Error Data Sources

The error panel is populated from two events:

NodeExecutionFailed — provides errorMessage, errorType, and nodeId of the failing node
WorkflowExecutionCompleted (status=failed) — provides the top-level failedNodeId and confirms the execution is terminal

Stack Trace Sanitization

Before displaying the stack trace, the same sanitize() function used by the Logs tab runs on the stack trace string. This prevents internal connection strings, API keys embedded in exception messages, or file system paths from being exposed in the UI:

// sanitize() strips:
// - credit card patterns (16-digit sequences)
// - JWT tokens (three base64url segments separated by dots)
// - known password field names and their values
// - Windows and Linux filesystem paths that contain user home directories
// - HTML tags

Navigate to Failed Node

A "View in Node List" link appears below the error message. Clicking it switches to the Node List tab filtered to show failed nodes only, with the failing node highlighted at the top.

Errors are Visible Without Opening the Inspector The Execution Status tab intentionally shows the top-level error because it is the first tab the user sees. This allows operators to diagnose common failures (timeouts, authentication errors) without needing to navigate into the Node Inspector.

← Execution Metadata Next: Node List Tab →