When using an email template with automation rules that sends out any values that have date/time variables as a part of those emails, those values are being rendered in the resulting email as UTC values, rather than being converted to the local timezone of the user. This becomes confusing for the user to know what times are accurate for items like:
and so forth
All date time values are stored in UTC in the database. The defect is that the template is simply re-rendering those exact values, rather than converting them to the timezone of the user reading the email.
Engineering is currently reviewing the problem. The workaround is to manually convert those values when the email is received to know the local time and date.