Skip to content

fix: catch UiPathBaseRuntimeError and add error category to I/O panel#68

Merged
cristipufu merged 1 commit intomainfrom
fix/structured-error-panel
Feb 16, 2026
Merged

fix: catch UiPathBaseRuntimeError and add error category to I/O panel#68
cristipufu merged 1 commit intomainfrom
fix/structured-error-panel

Conversation

@cristipufu
Copy link
Member

Summary

  • Fixed: LangGraphRuntimeError (extends UiPathBaseRuntimeError, not UiPathRuntimeError) was falling through to the generic except Exception handler, resulting in code="Unknown" in the error panel. Now catches UiPathBaseRuntimeError to properly surface structured error info.
  • Added: category field (User, System, Deployment, Unknown) to error serialization, TypeScript types, and error panel UI as a badge next to the error code.

Test plan

  • Run a LangGraph graph that triggers GraphRecursionError and verify the error panel shows LangGraph.GRAPH_LOAD_ERROR code, "Graph recursion limit exceeded" title, and "User" category instead of "Unknown"
  • Verify other runtime errors (e.g. InvalidUpdateError, EmptyInputError) still display correctly
  • Verify generic Python exceptions still fall through to the except Exception handler with code="Unknown"

🤖 Generated with Claude Code

LangGraphRuntimeError extends UiPathBaseRuntimeError (not UiPathRuntimeError),
so errors like GraphRecursionError fell through to the generic Exception handler
which used code="Unknown". Now catches the base class and surfaces the structured
code, title, detail, and category in the error panel.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@cristipufu cristipufu merged commit 64a2886 into main Feb 16, 2026
11 checks passed
@cristipufu cristipufu deleted the fix/structured-error-panel branch February 16, 2026 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments