Error handling issues

Describe the bug:
The application lacks proper error handling, leading to uncaught runtime errors and generic 500 Internal Server Error responses.

To Reproduce:

1. Trigger an error condition in the application (e.g., accessing a non-existent database table).
2. Observe the server response for error handling behavior.

Expected behavior:

• Errors should be caught and handled gracefully, preventing application crashes and providing informative error messages to clients.
• Server responses should include specific error codes and messages to aid in troubleshooting.

Additional context:

• The current lack of robust error handling undermines application reliability, maintainability and security.
• Users may experience frustration due to unclear error messages and unexpected application behavior.
• Developers face challenges in diagnosing and fixing issues efficiently, leading to longer resolution times.