Problem
The RAG pipeline fails silently in several edge cases, returning empty or malformed responses
with no user-facing error message.
Known Failure Scenarios
Expected Behavior
- Each pipeline stage should have a typed error boundary
- User sees a clear, actionable message when search/extraction fails
- Citations should be validated before rendering
- SSE timeout should trigger a graceful UI reset
Suggested Approach
- Wrap each stage (search → scrape → chunk → synthesize) in try/catch with typed errors
- Add a
PipelineError type with stage + reason fields
- UI: show partial results + error banner instead of blank screen
Labels
bug reliability help wanted
Problem
The RAG pipeline fails silently in several edge cases, returning empty or malformed responses
with no user-facing error message.
Known Failure Scenarios
[1]references in UIExpected Behavior
Suggested Approach
PipelineErrortype with stage + reason fieldsLabels
bugreliabilityhelp wanted