Hi All,
I hope FME will clean up posts after this…
In Australia and tried posting on the 26th, 27th and 28th(today).
I struck out on the ‘Are you smarter than ChatGPT’ quiz… the timed aspect was a killer.
Hi All,
I hope FME will clean up posts after this…
In Australia and tried posting on the 26th, 27th and 28th(today).
I struck out on the ‘Are you smarter than ChatGPT’ quiz… the timed aspect was a killer.
Still didn’t active the August Calendar Badge. :(
Also in Australia and I think I just missed out by an hour! It’s my last badge!
Yeah, was my last one as well…. other than the group ChatGPT one.
No good for the completionist in me.
I even changed my computer timezone with no luck.
It probably only works on Pacific business-hours?
Normally it works if you account for timezone differences and my current post would be 2 hours to late.
As far as I can tell it is UTC.
Whenever I get an alert about a new post, the payload includes the datetime of publication. I basically strip off the time part and the year, and just check if it is the correct day/month.
I believe that the platform (Gainsight) returns UTC. It wouldn’t make sense to return local time for either the user or Safe. So changing your computer timezone wouldn’t make a difference.
But when I hit the send button below, a workspace will run, and I’ll check to see what datetime it logs.
I can’t calculate your local time because I don’t have enough information. Plus, I figure that with a 24 hour window everyone in the world has a window of opportunity.
I deliberately made this one occur on a Wednesday so that no-one would have already started the weekend.
But, yeah, Apologies if it was problematic. I’ll check job logs to see if any failed, but I get automated warnings, so I don’t think so.
Mark
Yes, the Automation payload for my previous comment includes:
"repliedAt":"2025-08-28T17:34:27+00:00"
So it’s definitely UTC. The current time where I am is 12:39 (CDT) in Manitoba and 10:39 (PDT) in Vancouver.