500 Internal Server Error encountered

[Akanksha-Shahi]

### Title: [BUG]: 500 Internal Server Error encountered

Description

The application is throwing a 500: Internal Server Error, as shown in image_350650.png. This prevents users from completing their request and degrades the overall reliability of the platform.

Reproduction Steps

1. Navigate to the [Page Name, e.g., Profile or Dashboard].
2. Perform the action: [e.g., submitting the form / clicking the roadmap button].
3. Observe the server error page.

Proposed Investigation Plan

1. Log Analysis: I will investigate the server-side logs to identify the exact stack trace causing the 500 error.
2. Exception Handling: Implement robust try-catch blocks on the backend to handle the failure gracefully (e.g., returning a 400-series error or a custom error message instead of crashing).
3. Database/Service Validation: Verify if the failure is caused by an unhandled database query or an external API timeout.

Could you please assign this issue to me? I am eager to help debug and stabilize this endpoint.
/assign under GSSoC 26

[github-actions]

Thank you for opening your first issue in DevPath.

Please make sure to:

• Read CONTRIBUTING.md
• Wait for assignment before starting work
• Follow repository guidelines carefully

Happy contributing.

[kotebhakti30]

Hi @komalharshita, I would like to work on this issue under GSSoC'26.

Description

After reviewing the issue, I understand that the application is throwing a 500: Internal Server Error which prevents users from completing their requests and degrades the overall reliability of the platform. The root cause appears to be unhandled exceptions on the backend — either from a failing database query, missing input validation, or an unguarded async operation that crashes the server instead of returning a proper error response.

Proposed Fix

Investigate the server-side logs to identify the exact route and stack trace causing the 500 error
Wrap the failing route handler(s) in try-catch blocks to prevent unhandled exceptions from crashing the server
Return a proper 400 or 404 error response with a descriptive message instead of letting the server throw a 500
Add input validation on the affected endpoint to catch bad or missing request data before it reaches the database or service layer
Verify whether the failure is caused by an unhandled database query rejection or an external API timeout and handle each case appropriately

Expected Outcome

The endpoint no longer returns a 500: Internal Server Error for the failing request
Users receive a descriptive and appropriate error response instead of a generic server crash
The backend handles edge cases gracefully without crashing
All changes are confined to the affected route handler(s) with no breaking changes to existing functionality

Please assign this issue to me. Thank you!

[kotebhakti30]

/claim
/assign

[NirvanJain]

Heyy @Akanksha-Shahi
I would like to work on this issue under GSSoC 2026.
I have prior experience with open-source contributions and would be happy to work on this issue. Please assign it to me.
Thank you!

[nensii21]

/assign

[Saniya30pawar]

Hi @komalharshita, I would like to work on this issue under GSSoC'26.