Internal users may receive emails with incorrect dates being resolved in date tokens.
Reproducing the Issue
In the below example, you may see a situation where the [[OFFER_RESPONSE_DATE]] token resolves a date that is in the future, compared to the date the email was received:
The system will always consider the instance time zone, regardless of what time the action was performed by the candidate/ system user that might be located in other time zone.
In this specific scenario, the candidate approved an offer located in Canada, around 08:00 PM (Jan 15th) and this triggered the above email. The referred instance in this example is a DC5/12 instance located in Rotterdam, thus following the Rotterdam time zone. The time the candidate approved the same offer in Canada, was actually 02:00 AM (Jan 16th) in Rotterdam and this is why we see the discrepancy in the dates. This is a very specific example, but several other date issues may occur to tokens due to the same behavior. Please, have it in mind when facing scenarios like the one discribed above.
The system is designed to always consider the instance time zone. Although sometimes confusing, such behavior is currently considered expected and no actions may be taken to have it changed.
Date tokens Different date , KBA , LOD-SF-RCM , Recruiting Management , Problem