Date filter keeps timing out when given 2026 dates

Get Help
1

I’m trying to pull the number of rows from a model that are created in 2026. I tried putting a date filter on my column “date creation time” (which is a timestamp data type in my Metabase model), and it works successfully for any value(s) prior to 2025.

I’m trying to pull the number of rows in all of 2026, so I tried the following date filters:

  • After Dec 31, 2025
  • Between Jan 1, 2026 and Dec 31, 2026
  • Created This Year

I always get the error “Your question took too long. We didn't get an answer back from your database in time, so we had to stop. You can try again in a minute, or if the problem persists, you can email an admin to let them know.”

The only exception is when I make 2026 date filters on days that have already happened/are happening. So I can do Between Jan 1, 2026 and Jan 3, 2026. But the weird thing is that I can’t do Between Jan 1, 2026 and Feb 10, 2026? But I can do On Feb 10, 2026 successfully? Not sure what’s going on.

I’m running Metabase version 0.58.5. Thanks in advance and take care!

2

Do you have any performance problems if you write a native query with the same time ranges?

Trying to check if the problem is from the database due to a missing index, bad table partitioning, etc.

You may have to increase the query timeouts in your reverse proxy if the queries are timing out before 20 minutes.