fix: display exception message in trace output column when outputs is nullfix: display exception message in trace output column when outputs is…#4747
Conversation
… null When a trace span contains an exception event but no outputs, the output column in the observability table showed an em dash (—). This fix checks for exception events and displays the exception message/type in red when outputs are absent. Fixes Agenta-AI#4731
|
@unfitcoder101 is attempting to deploy a commit to the agenta projects Team on Vercel. A member of the Team first needs to authorize it. |
|
✅ Thanks @unfitcoder101! This PR now meets the contribution requirements and has been reopened. A maintainer will review it soon. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Disabled knowledge base sources:
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe "Outputs" column renderer in the observability table is updated to detect a missing ChangesException fallback in Outputs column
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Display exception message in the trace output column when outputs are null.
Previously, when a trace span had an exception event but no outputs,
the output column showed an em dash (—). Now it shows the exception
message/type in red so users can immediately see what failed without
opening the trace detail view.
Changes
getObservabilityColumns.tsxto checkrecord.eventsfor exception events when outputs are nullexception.messageorexception.typeas fallback textDemo
Issue
Fixes #4731