3746938 - Incorrect name in token signature of rejection emails — Recruiting Management

• Candidates receive rejection emails where the name populated by user tokens in the signature is incorrect.
• The [[USER_FIRSTNAME]] and [[USER_LASTNAME]] tokens show a different user's name than the person who performed the last status change sending the email.
• No error message is displayed.

SAP SuccessFactors Recruiting Management

1. Move an application to the Disqualification status by user A.
2. Move the same application to another disqualification status by user B, with a status email configured on this second status.
3. Status triggered email is sent to the candidate and observe that the signature tokens [[USER_FIRSTNAME]] [[USER_LASTNAME]] populate with user A’s name instead of user B’s.

• When an application is first moved into a disqualification status, the system creates a delayed email alert that stores owner, date, and status.
• On a subsequent move to another disqualification status, the same alert is updated for date and status only; the owner is not updated.
• Because the owner is not updated, the email still references the username from the first alert, resulting in the wrong name in the token signature.

1. Note that a product fix updates the alert handling so that, during alert updates, the owner name is updated together with status and date.
2. Plan to consume the fix with the 2H2026 release.
3. If you are impacted before the 2H2026 release, contact support to request an appropriate patch evaluation for your environment.

recruiting, rejection email, wrong name, token signature, user firstname, user lastname, status email, disqualification status, email alert owner, delayed email, signature tokens, incorrect sender name, rejection by recruiter, better applications, rcm emails , KBA , LOD-SF-RCM-EML , Recruiting Emails and Notifications , Problem