Bug-005-Re-uploading a resume for a candidate who has already applied to the same job does not show a duplicate/error message; instead the "Processing" banner gets stuck indefinitely with no resolution.

Bug-006

Bug Summary:
Re-uploading a resume for a candidate who has already applied to the same job does not show a duplicate/error message; instead the "Processing" banner gets stuck indefinitely with no resolution.

Environment: Staging
Module: Resume Upload — Duplicate Detection

Preconditions
User is logged in.
Candidate "Deep Saha" already exists as a scored applicant for job "DevOps" (Score 6.1, Moderate fit).

Steps to Reproduce
Login to the application.
Open job "DevOps" with Deep Saha already listed as an existing applicant.
Click "Upload resumes" and select the identical Deep-Saha-Resume file again.
Observe the "Processing 1 resume..." banner and Applicants/Scored/Awaiting score counters.
Wait 60+ seconds and re-check.
Manually refresh the page and re-check.

Expected Result
System should detect the duplicate candidate/resume and show a clear error or warning message (e.g., "This candidate has already applied to this job"), without leaving the UI in a stuck processing state.

Actual Result
Banner remains stuck on "Processing 1 resume..." for 75+ seconds with zero change; Applicants/Scored/Awaiting counters never update; no error shown; no duplicate entry created. Banner only disappears after a manual page refresh (F5) — it never auto-clears or auto-updates on its own.

Test Data
Job "DevOps"; duplicate upload of "DevOps_Deep_Saha_Resume" file (already an existing applicant).

Severity
High

Priority
High

Attachment:

https://github.com/user-attachments/assets/f43cdf80-f253-4db4-8d6a-dbbbe53b2a84