I anticipate that we will frequently develop processes that incorporate "Run Date" within Rules, Data Designer, and Journey Orchestrator.
Currently, Gainsight processes operate based on the UTC time zone specification.
For example, consider the result of the following Rule processing:
Tenant time zone: UTC+9
Equation: Add/Subtract (Run Date, +, 7, days)
Run Date: 2025/5/10 8:00 → Resulting date from Run Date(): 2025/5/16
Run Date: 2025/5/10 9:00 → Resulting date from Run Date(): 2025/5/17
The expectation is that the function should return the date in the tenant time zone (2025/5/10) plus 7 days, which would be 2025/5/17. However, because the specification is based on UTC, in case 1, the "Run Date" effectively becomes 2025/5/9 23:00 UTC (9 hours earlier than 2025/5/10 8:00 JST). As a result, the function returns 2025/5/16, which is one day earlier than anticipated.
If processing could be performed in the tenant's local time zone, it would eliminate the need to account for time zone differences. This would prevent issues caused by oversight and avoid unnecessary manual effort.
I hope you will consider modifying this specification!!!!😑
If you have experienced similar issues or have similar thoughts, please share your comments.