[BUG] : Implement Global Error Boundary and Centralized Exception Handling

[codecrafted1]

Implement Global Error Boundary and Centralized Exception Handling

Description

The application currently lacks a centralized error handling strategy for runtime exceptions and asynchronous failures. Unhandled errors can result in blank screens, broken user flows, and a poor user experience.

A global error handling mechanism should be implemented to ensure the application fails gracefully and provides meaningful feedback to users while capturing diagnostic information for debugging.

Problem Statement

• Unhandled runtime exceptions can crash the application.
• Unhandled promise rejections may leave the UI in an inconsistent state.
• Errors are not captured through a centralized logging mechanism.
• Users may encounter blank screens instead of actionable feedback.
• Debugging production issues becomes difficult without proper error reporting.

Proposed Solution

Frontend

• Create a reusable ErrorBoundary component.
• Wrap the root application with the Error Boundary.
• Design a user-friendly fallback UI.
• Handle unexpected rendering errors gracefully.

Global Exception Handling

• Capture unhandled promise rejections.
• Capture unexpected runtime errors.
• Log errors through a centralized logging utility.

Logging

• Implement a centralized logger service.
• Prevent exposure of sensitive information in logs.
• Provide structured error reporting for debugging purposes.

Acceptance Criteria

• Application does not crash to a blank screen on component errors.
• A fallback UI is displayed when an unexpected error occurs.
• Unhandled promise rejections are captured and logged.
• Runtime exceptions are logged through a centralized mechanism.
• Error details exposed to end users are sanitized.
• Existing application functionality remains unaffected.

Expected Benefits

• Improved application stability.
• Better production debugging.
• Enhanced user experience.
• More maintainable error handling architecture.

Labels

• bug
• enhancement
• architecture
• error-handling
• gssoc

[codecrafted1]

@devloperdevesh /assign

[codecrafted1]

Hi! Thanks for merging my PR. I noticed that the GSSoC labels haven't been added to the PR yet. Because of that, the contribution isn't showing up on the GSSoC leaderboard. Could you please add the appropriate labels (GSSoC and any other required project labels) to this PR? *Username:* codecrafted1 *Project:* EnterpriseRAG-AI *PR: *#123 I'd really appreciate it. Thank you for your time and for reviewing the contribution!

…

On Tue, Jul 14, 2026 at 2:23 PM Devesh Chauhan ***@***.***> wrote: Closed #122 <#122> as completed via #123 <#123>. — Reply to this email directly, view it on GitHub <#122?email_source=notifications&email_token=BY3VE4PY5UK3SMTBN2BQH4T5EXYHPA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZZGUZDIMBUGI4TPJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#event-27952404297>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BY3VE4LKGMJNKY4ORD5M32D5EXYHPAVCNFSNUABGKJSXA33TNF2G64TZHMYTCMRWGYZDIOBRGQ5US43TOVSTWNBWHAYTQNJXGU2TRILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BY3VE4LXZOEPIWUU3KLUS5T5EXYHPA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZZGUZDIMBUGI4TPJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BY3VE4LPFKNOAOERUDM2PMT5EXYHPA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZZGUZDIMBUGI4TPJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.*** com>