Tasks are not running in the MetaBase scheduler

1

Hello everybody!

All tasks in the scheduler were last started on 12/19/2025

Restart date: 15.12.2025
Tasks were completed for 5 days (15.12 - 19.12.2025)

The time of the next launch is indicated correctly, but the tasks do not start at this time after 12/19/2025 (as seen in the screenshot).

It's also confusing that the time zone (+3) is not specified. After the restart, the time zone is displayed correctly.

How can this be fixed?

21
212086×194 47.3 KB

22
222093×345 77.4 KB

23
232103×345 80.9 KB

{
"browser-info": {
"language": "ru-RU",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36 OPR/125.0.0.0",
"vendor": "Google Inc."
},
"metabase-info": {
"databases": [
"postgres",
"sqlserver"
],
"run-mode": "prod",
"plan-alias": "",
"version": {
"date": "2025-12-11",
"tag": "v0.57.6",
"hash": "e9e9771"
},
"settings": {
"report-timezone": null
},
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "12.22 (Debian 12.22-1.pgdg120+1)"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.7.7"
}
}
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "21.0.9+10-LTS",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "21.0.9",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "21.0.9+10-LTS",
"os.name": "Linux",
"os.version": "4.15.0-213-generic",
"user.language": "en",
"user.timezone": "GMT"
}
}

2

check the status in the metabase database, are those tasks not in an error state?

3

Do you have instructions?
Where can I see it?

4

Connect to the Metabase app database and issue these queries:

select trigger_state, count(*) from qrtz_triggers group by trigger_state;
select trigger_state, trigger_name, description from qrtz_triggers ;

You will get a count of the active triggers, and a table detailing the state of each. If the first query returns any BLOCKED triggers that don’t go away after a couple of seconds then one of the tasks has crashed and is blocking the scheduler from executing future tasks. Check the Metabase log for when and what happened when the thread crashed.

If you can’t find the crashed thread, set up a cron job to run those queries every few minutes and record the output. Keep that running until a task crashes, then you can likely go back through that output and find what job is stuck running.

You will have to restart Metabase when a thread crashes as there is no way to restart Quartz from inside Metabase.

1 Like
5

Thank you so much for the detailed reply!

I already restarted MetaBase yesterday.
I will wait for the next case to check.