This content has been marked as final. Show 7 replies
I had this issue earlier this week. There was a bug that made it so the if someone used the token in a different time zone, it would revert the token to that time zone. (For us, every calendar token was off by 5 hours)
They told me that this was fixed but I'd have to go in and manually update all tokens back to correct time. I'd double-check with support on this.
Thank you!! I thought we were missing something. And good to know when it will be fixed too cos it is causing major issues for us too, our calendar tokens were off by 10hrs.
I'm also experiencing this issue. Really frustrating, as I tested an email and had the ics token not do the math to local time, then sent out the blast and got hammered from everyone saying their Outlook added 3 hours. When will the bug be resolved?
This issue has been fixed as of 7/9/2013. Specifically, going forward all new calendar tokens will not be effected by the issue.
For all old tokens that are still effected by the issue, you will need to edit and then save the token manually to fix.
Sorry for the inconveniences.
Thank you for confirming the fix. However we sent an email on 07/12/2013 and the error still occured, I am not sure how as the campaign was reviewed after the bug was fixed on 07/09/2013.
This error is still occuring for me. I set up the token last week; tested it over the last few days. I set it up in CST and that is also my time zone; it is saving as the wrong time for me and others in CST.
Please submit a new case to Support with details and specifics.