Metabase dashboards change to tomorrow at 5pm mst

When we update metabase to v0.38.0, all of our dashboards that are set to today, change to tomorrow at 5pm mst. We have our metabase instance timezone set up for MST time but this still happens. Is there something we are missing or a way to fix this?

Hi @BrettJohnson2
Please post “Diagnostic Info” from Admin > Troubleshooting.
Which version did you upgrade from?
I’m not sure I understand what you mean by “change to tomorrow at 5pm mst” - do you mean the results, or a filter, or …?

“browser-info”: {
“language”: “en-US”,
“platform”: “MacIntel”,
“userAgent”: “Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36”,
“vendor”: “Google Inc.”
“system-info”: {
“file.encoding”: “UTF-8”,
“”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “11.0.10+9”,
“java.vendor”: “AdoptOpenJDK”,
“java.vendor.url”: “”,
“java.version”: “11.0.10”,
“”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “11.0.10+9”,
“”: “Linux”,
“os.version”: “4.14.62-65.117.amzn1.x86_64”,
“user.language”: “en”,
“user.timezone”: “GMT”
“metabase-info”: {
“databases”: [
“hosting-env”: “elastic-beanstalk”,
“application-database”: “postgres”,
“application-database-details”: {
“database”: {
“name”: “PostgreSQL”,
“version”: “10.13”
“jdbc-driver”: {
“name”: “PostgreSQL JDBC Driver”,
“version”: “42.2.18”
“run-mode”: “prod”,
“version”: {
“date”: “2021-02-16”,
“tag”: “v0.38.0”,
“branch”: “release-x.38.x”,
“hash”: “471aa51”
“settings”: {
“report-timezone”: “US/Mountain”

what is happening is all of our dashboards by default are filtered for today. As soon as 5pm hits mst our dashboards go blanks because the today filter acts like it is tomorrow. We upgraded from V0.33.6 i believe. This usually happens though everytime we upgrade so we roll back.

@BrettJohnson2 Timezone are a pesky thing.

Which version of MySQL
What’s the timezone of MySQL?
And which column type in MySQL is the filtered on the dashboard referenced to?

I know there’s a problem on Postgres, when the columns doesn’t contain timezone information, then Metabase will treat them with the instance timezone (which is set to GMT, since you’re likely using Docker).