Error Details
The Error Details section only appears when the selected node's status is failed. It shows the exception type, error message, and an expandable stack trace — giving more detail than the Execution Status tab's top-level error summary.
Error Fields
| Field | Source | Notes |
|---|---|---|
| Error Type | NodeExecutionFailed.errorType | C# exception class name (e.g., HttpRequestException) |
| Error Message | NodeExecutionFailed.errorMessage | Exception message text, sanitized before display |
| Stack Trace | NodeExecutionFailed.stackTrace (if available) | Expandable; sanitized; shows first 50 frames |
| Retry Exhausted? | Derived from retryCount vs retry policy max | Shows "Retry policy exhausted" label if all retries used |
| willRetry | NodeExecutionFailed.willRetry | True if the engine will retry; false if this is the final failure |
willRetry: true
If the node failed but the retry policy has remaining attempts, a NodeExecutionFailed event is emitted with willRetry: true. The Node Inspector shows these intermediate failures as a history list — you can see each attempt's failure reason before seeing the final outcome. This helps identify whether a node is intermittently failing.
Node-Level vs Execution-Level Errors
The Node Inspector's Error Details shows the error for the specific node. The Execution Status tab shows the top-level error (which is the error from the node that caused the execution to terminate). For simple workflows these are the same. For workflows with error-handling nodes (try-catch), the execution may complete successfully even though individual nodes errored — the Node Inspector for an errored node will show the error regardless of the overall execution outcome.