Pulse failing after every 4 day run

The above configuration is before we decided to updated the timezone.
I am pasting the current timezone.

{
“browser-info”: {
“language”: “en-US”,
“platform”: “MacIntel”,
“userAgent”: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36”,
“vendor”: “Google Inc.”
},
“system-info”: {
“java.runtime.name”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “11.0.3+7”,
“java.vendor”: “AdoptOpenJDK”,
“java.vendor.url”: “https://adoptopenjdk.net/”,
“java.version”: “11.0.3”,
“java.vm.name”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “11.0.3+7”,
“os.name”: “Linux”,
“os.version”: “4.14.106-97.85.amzn2.x86_64”,
“user.language”: “en”,
“user.timezone”: “US/Pacific”
},
“metabase-info”: {
“databases”: [
“snowflake”
],
“hosting-env”: “unknown”,
“application-database”: “postgres”,
“run-mode”: “prod”,
“version”: {
“date”: “2019-11-19”,
“tag”: “v0.33.6”,
“branch”: “release-0.33.x”,
“hash”: “be1e0e1”
},
“settings”: {
“report-timezone”: “Canada/Eastern”
}
}
}

I am extremely sorry to paste the old configuration in issue reported.
Just now i updated the issue.

1 Like

@devD Just for the fun of is, could you try a timezone (TZ database name) from this list instead of US/Pacific, which is deprecated along with Canada/Eastern.
https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
I’ve seen some really, really strange issues with timezones - for instance this entire topic: Empty response on SQL-Server queries containing DATETIME

I don’t think it’ll change anything, but just wanna make sure it’s not that.