2103770 - Recruiting email trigger tokens Requisition Posted or Requisition Posting Expiration Upcoming not working - Recruiting Management

Why are tokens [[JOB_REQ_ID]] and [[JOB_REQ_TITLE]] for “Requisition Posted” or “Requisition Posting Expiration Upcoming" in Recruiting Email Triggers not working?

SAP SuccessFactors Recruiting Management

The email triggers for "Requisition Posted" and "Requisition Posting Expiration Upcoming" operate asynchronously. Posted job requisitions do not trigger emails immediately. Instead, the system sends consolidated emails at the end of each day to all recipients.

These consolidated emails contain information for ALL job requisitions posted within that day. Therefore, all job requisition-related tokens (such as [[JOB_REQ_TITLE]] and [[JOB_REQ_ID]]) must be resolved for every job requisition included in the email.

To enable this functionality, customers must wrap their email template content with the mandatory tokens [[BEGIN_REPEAT]] and [[END_REPEAT]].

Example:
Dear user, [[BEGIN_REPEAT]] Requisition # [[JOB_REQ_ID]] and title [[JOB_REQ_TITLE]] has been posted OR has expired. [[END_REPEAT]]

NOTE: The job requisition ID and title tokens must be positioned between the begin and end repeat tokens.

SF, SuccessFactors, RCM, job, postings, token, not, populating, email triggers, asynchronous, consolidated emails, job requisitions, tokens, BEGIN_REPEAT, END_REPEAT, JOB_REQ_ID, JOB_REQ_TITLE, template  , KBA , LOD-SF-RCM-EML , Recruiting Emails and Notifications , How To