Email and slack schedules are not getting triggered

Get Help FAQ
1

log:
25T12:31:26+05:30 INFO org.quartz.impl.jdbcjobstore.JobStoreTX Handling the first 20 triggers that missed their scheduled fire-time. More misfired triggers remain to be processed. [5ab22be8-364e-43db-a36a-ba5e9e6b9e68] 2025-11-25T12:31:26+05:30 INFO org.quartz.impl.jdbcjobstore.JobStoreTX Handling 10 trigger(s) that missed their scheduled fire-time. [5ab22be8-364e-43db-a36a-ba5e9e6b9e68] 2025-11-25T12:31:26+05:30 DEBUG metabase.server.middleware.log GET /api/database/210/autocomplete_suggestions 200 19.5 ms (6 DB calls) App DB connections: 1/15 Jetty threads: 14/250 (54 idle, 0 queued) (791 total active threads) Queries in flight: 26 (0 queued)

I checked inside mtebase table
MySQL [metabase]> SELECT TRIGGER_STATE, COUNT()
-> FROM QRTZ_TRIGGERS
-> GROUP BY TRIGGER_STATE;
+---------------+----------+
| TRIGGER_STATE | COUNT() |
+---------------+----------+
| BLOCKED | 222 |
| WAITING | 8 |
+---------------+----------+

can anyone help me to fix this

2

Does it seem to be all tasks, or one in particular? Try grouping by job_name and trigger_state.

EDIT: BLOCKED state means the job is already running in another thread. If it got stuck or crashed in some way that doesn’t release the thread, the other queued instances will stay in BLOCKED. Try restarting Metabase, that should reset the wait states on the jobs. If you have multiple Metabase instances using the same app database, try to restart them all at once (or shut them all down then start them back up).

3

Thanks, I have tried restarting the metabase, now I Don’t see any Blocked entries now

MySQL [metabase]> SELECT TRIGGER_STATE, COUNT() FROM QRTZ_TRIGGERS GROUP BY TRIGGER_STATE;
+---------------+----------+
| TRIGGER_STATE | COUNT() |
+---------------+----------+
| WAITING | 230 |
+---------------+----------+
1 row in set (0.001 sec)

But after sometimes I got it back

MySQL [metabase]> SELECT TRIGGER_STATE, COUNT() FROM QRTZ_TRIGGERS GROUP BY TRIGGER_STATE;
+---------------+----------+
| TRIGGER_STATE | COUNT() |
+---------------+----------+
| BLOCKED | 127 |
| WAITING | 103 |
+---------------+----------+
2 rows in set (0.001 sec)

4

We need to figure out why one of the jobs is getting stuck. You’re sure you’re not getting anything abnormal in the log? OutOfMemory exceptions crashing threads and network problems would be the most likely causes.

Do you have multiple Metabase instances accessing the same app database (i.e., running in cluster mode)?