[BUG] Notification creation fails silently due to schema mismatch when a new answer is posted

[akashnayak812]

Problem

When a user posts a new answer, the system tries to create a notification for the question owner but it fails silently. The data payload passed to Notification.create() doesn't match the fields in the Notification Mongoose schema, so question owners never receive notifications for new answers.

Steps to Reproduce

1. Log in as User A, post a question
2. Log in as User B, post an answer to that question
3. Check User A's notifications — nothing appears
4. Check server logs — a Mongoose validation error is thrown but not surfaced to the client

Root Cause

In answersController.js, the notification object likely passes fields that don't match the exact field names/types defined in the Notification schema.

Expected Behavior

Posting an answer should create a valid notification for the question owner that appears in real-time and persists in the database.

Proposed Fix

1. Audit the Notification schema fields and required types
2. Update the notification payload in answersController.js to match the schema exactly
3. Add try/catch around Notification.create() with proper error logging
4. Add a test case verifying notification creation on answer submit

[akashnayak812]

I want to reslove this issue please accept me
to contribute

[Manasvi05Dadhich]

hey i have worked on similar project, i would like you solve this issue, could you please assign this to me ?

[adyas0628-rgb]

Hi, I would like to work on this issue, please assign it to me

[deeptiatre]

hey @Ashmita1206 , I would love to solve this issue, as I have already done some projects like this, so could you assign it to me.

[Sanjay-Hub-Dev]

Hi @Ashmita1206 👋

I would like to work on this issue under GSSoC 2026.

🧩 Issue Understanding

After reviewing the issue description, it appears that notification creation during new answer submissions is failing silently due to a mismatch between the notification schema and the payload/data being generated in the answer creation flow.

This can lead to missing user notifications while also making debugging difficult because the failure is not surfaced properly.

🔍 Implementation Plan

I’m planning to:

• Trace the answer submission → notification creation workflow
• Inspect the notification schema and related payload structure
• Identify mismatched or missing fields causing silent failures
• Add proper validation/error handling around notification creation
• Ensure notification generation works consistently when new answers are posted
• Preserve the existing answer posting workflow and application behavior

📂 Files Likely Involved

• Notification schema/model files
• Answer creation controller/service logic
• Notification creation utility/service files

✅ Validation

• Test notification creation flow after posting new answers
• Verify proper schema compatibility and database insertion
• Ensure failures are handled gracefully without silent breakdowns
• Confirm no regression in existing answer submission functionality

I’ll keep the fix focused, reliable, and aligned with the current backend architecture of StackIt.

Please assign this issue to me 🚀