Unverified50% confidenceFactExact time
Tracing marks a span as failed only when an exception escapes that span's code block; if the exception is handled inside the try block, the span keeps its default status.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe way to fix the signal lost by catching an exception is to actively re-mark inside the catch block, for example by calling span.recordException(e) and span.setStatus({ code: SpanStatusCode.ERROR }), and then decide whether to resume execution.72% similarUnverifiedBy default, if an item causes an error in a node, the entire run is interrupted and subsequent items are no longer processed.72% similarUnverifiedIf the framework has already erased the signal, no downstream check can restore the original error; the run-shape assertion provides a symptom, enough to send you back to the trace to diagnose the swallowed exception.63% similarUnverifiedIn the three complete cases that retained the text check, the idle agent FAILED all three, and the failure reasons were all related to text content, not the tool-call check.63% similarUnverifiedRecurring identical errors are a framework-level problem; each failure should be converted into a permanent rule rather than simply retried.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1009536API
curl https://kongchang.com/api/v1/knowledge/claims/1009536MCP
get_claim(id=1009536)