[BUG]: Jobs are not being applied to, despite log record's statements

[typhoonfire8]

Describe the bug

when looking through the terminal logs, upon assessing the suitability of the job, the logs will claim that the job has been applied to, corroborated within the success.json file, however when looking through the LinkedIn MyJobs section those jobs have not been applied to. Even for jobs with low suitability scores, the logs will show that they are being applied to and appended to the success.json file.

Steps to reproduce

No response

Expected behavior

the logs should accurately reflect that the job has not been applied to, and should not append those jobs to the success.json file and instead to the skipped.json file. That is unless those jobs were intended to be applied to, in which case the application needs to actually apply to those jobs

Actual behavior

the application is claiming jobs that aren't being applied, are in fact being applied to

Branch

other

Branch name

hotfix/v2024.11.23

Python version

3.11.5

LLM Used

Open AI

Model used

GPT-4o

Additional context

No response

[typhoonfire8]

2024-11-24 23:00:38.556 | INFO | ai_hawk.llm.llm_manager:is_job_suitable:706 - Job suitability score: 2
2024-11-24 23:00:38.557 | DEBUG | ai_hawk.llm.llm_manager:is_job_suitable:708 - Job is not suitable: The candidate does not meet the hard requirements for the position, as they lack the necessary experience in high-performance analog layout in advanced FINFET CMOS processes, as well as experience with EDA tools like Cadence, Mentor, and Synopsys. The resume indicates experience in general tech and project management but does not demonstrate any relevant IC layout design experience or knowledge of analog design principles.
2024-11-24 23:00:38.559 | DEBUG | ai_hawk.job_manager:write_to_file:407 - Writing job application result to file: success
2024-11-24 23:00:38.573 | DEBUG | ai_hawk.job_manager:write_to_file:438 - Job data appended to existing file: success
2024-11-24 23:00:38.575 | DEBUG | ai_hawk.job_manager:apply_jobs:400 - Applied to job: {removed for privacy}

[surapuramakhil]

@typhoonfire8 it's an existing bug. when job gets skipped due to job suitability it gets added to success.json instead of skipped.json

relevant PR #884

[github-actions]

This issue has been marked as stale due to inactivity. Please comment or update if this is still relevant.