This article describes a pretty specific scenario that might occur depending on the client emails configuration.
It is common to have system instances configured with Status Triggered Emails, that should be sent to candidates upon an application status change (when the applicant is moved across the application pipeline). If we forward a candidate to a requisition (search candidate database and forward them to the job), and the candidate does not apply to the job before being put in a status with the status triggered email, once the candidate completes their application in that step, they will end up receiving the trigger emails twice.
SuccessFactors Recruiting Management (all versions)
Reproducing the Issue
A Late Stage candidate was moved into New Applicant status, which triggered the first Email to the candidate (or a recruiting operator). Then once the candidate actually applied to the requisition, changing it from late stage applicant to an actual applicant, the system re-triggered the Status Triggered Email to the candidate.
- Forward any candidate to a job requisition;
- Move this late stage candidate to an application status. The candidate will receive the status triggered e-mail for the first time;
- Access this candidate account and apply to the same job. The candidate will then receive the status triggered e-mail for the second time, if the candidate happens to fall into the same candidate status it was before (e.g.:New Candidate).
Based on how the system is designed to work, this is a system expected behavior. We understand this may be misleading depending on how the customer system is configured and we are looking to have this added as an enhancement task (RCM-47166) in the future, but this is not considered a system defect for now, thus no action may be performed on customer or support side to have this changed.
Duplicated emails Duplicated status triggered emails , KBA , LOD-SF-RCM , Recruiting Management , Problem