Closed PorreKaj closed 4 years ago
Hmmm weird. I've seen this before and thought I fixed it. I'll take a look today!
Ah. I missed a spot where I needed to configure the "time zone resolver" to use NodaTime rather than the system time zones. Resolved in tonight's build.
Interesting info: Time zone configurations are crazy and they are different between Unix\Windows. Also, if you use the default Ubuntu docker container it doesn't contain ANY time zone configurations. Hence the need to introduce a time zone database like NodaTime to resolve timezones that work cross platform.
Describe the Issue
Disclaimer: I don't know if a cron schedule works either.
I scheduled a script for Every 15 minutes, but in the 'upcomming' tab, it says "Jan 1, 0001 12:00 AM" as next execution
debug console gives me:
To Reproduce
Be in EU timezone Create script Schedule script