I spread out my alerts, most are being delivered fine. Two that are set for the same time are not. I run them and they load fine, I then send the scheduled alert manually and it sends fine. But the scheduled alert just fails, instantly:
2025-04-15 07:00:00,122 INFO task.send :: {quartz-job-type=SendNotification} Sending notification 7 for subscription 7
The actual query takes about 2 minutes, nothing in the log after this for at least another 8 minutes and thats like someone else logging in.
TonyC
April 17, 2025, 1:48pm
2
Did this happen after an upgrade? What metabase version are you running? ... There was an issue open similar to that:
opened 01:39PM - 07 Apr 25 UTC
closed 11:23AM - 16 Apr 25 UTC
Type:Bug
Priority:P1
.Escalation
.Team/Workflows
Notifications
Cloud-Blocker:54
**Describe the bug**
Since upgrading to Metabase _v0.54.1_, scheduled alerts ar… e not being sent. This issue affects both newly created alerts and those existing prior to the upgrade, across email and Slack notifications. In the **Troubleshooting > Tasks** section, the `notification-trigger` task shows a status of `"success"`, but no notifications are received. Manually triggering the alert using the "Send now" button works as expected.
Example payload for the scheduled alert:
```json
{
"trigger_type": "notification-subscription/cron",
"notification_subscription_id": 144,
"cron_schedule": "0 04 * * * ? *",
"notification_ids": [144]
}
```
**Logs**
No specific errors appear in logs. The `notification-trigger` task status is `"success"` but the notifications are not sent.
**To Reproduce**
1. Upgrade to Metabase _v0.54.1_.
2. Create a new alert or use an existing one.
3. Set the alert condition to "When this question has results."
4. Schedule the alert for a specific time.
5. Wait for the scheduled time — no notification is received.
6. Click "Send now" — notification is successfully sent.
**Expected behavior**
Scheduled alerts should send notifications via configured channels (email/Slack) at the scheduled time.
**Screenshots**
N/A
**Severity**
High — This is blocking scheduled alerting functionality.
**Additional context**
N/A
**Metabase Diagnostic Info**
```json
{
"browser-info": {
"language": "en-US",
"platform": "Linux x86_64",
"userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
"vendor": "Google Inc."
},
"metabase-info": {
"databases": [
"postgres",
"bigquery-cloud-sdk"
],
"run-mode": "prod",
"plan-alias": "",
"version": {
"date": "2025-04-02",
"tag": "v0.54.1",
"hash": "774e5a3"
},
"settings": {
"report-timezone": "UTC"
},
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "17.4"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.7.5"
}
}
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "21.0.6+7-LTS",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "21.0.6",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "21.0.6+7-LTS",
"os.name": "Linux",
"os.version": "6.6.72+",
"user.language": "en",
"user.timezone": "GMT"
}
}
```
bit you're saying it "fails" but i don't see errors in the logs, am i missing something?