Archived Pulse Still Sending Emails

Get Help
1

Hi Everyone,

Our Metabase instance has a pulse that was archived on Tuesday. The underlying question was archived as well. When I look in our Postgres RDS for our metabase application (setup on ELB), I see that the pulse and question were both archived, and when I look at the query_execution table there’s no record of the pulse sending after Tuesday. The users who were receiving an email from the pulse are still receiving the pulse emails, though. Does anyone know what other triggers in the application are setup to send pulses, and why they would still fire despite the archival? Also, why there’s no log of the query execution?

1 Like
2

Hi @ksapelak

Which version of Metabase? Please post “Diagnostic Info” from Admin > Troubleshooting.

While this shouldn’t happen, you might be able to see if there’s a task lingering around, which might be causing something. Admin > Troubleshooting > Tasks

You should be able to see the pulse run in query_execution. Maybe there’s errors in Admin > Troubleshooting > Logs?

3

Here’s our diagnostic info. Looks like we’re on version 0.33.7.3

{
“browser-info”: {
“language”: “en-US”,
“platform”: “MacIntel”,
“userAgent”: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36”,
“vendor”: “Google Inc.”
},
“system-info”: {
“java.runtime.name”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “11.0.3+7”,
“java.vendor”: “AdoptOpenJDK”,
“java.vendor.url”: “https://adoptopenjdk.net/”,
“java.version”: “11.0.3”,
“java.vm.name”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “11.0.3+7”,
“os.name”: “Linux”,
“os.version”: “4.14.152-98.182.amzn1.x86_64”,
“user.language”: “en”,
“user.timezone”: “GMT”
},
“metabase-info”: {
“databases”: [
“postgres”,
“snowflake”,
“h2”,
“redshift”
],
“hosting-env”: “elastic-beanstalk”,
“application-database”: “postgres”,
“run-mode”: “prod”,
“version”: {
“date”: “2019-12-16”,
“tag”: “v0.33.7.3”,
“branch”: “release-0.33.x”,
“hash”: “7ee7193”
},
“settings”: {
“report-timezone”: “UTC”
}
}
}

4

@ksapelak
Latest release is 0.35.3

There has only been one report of something similar lately, which turned out to be an issue somewhere else: https://github.com/metabase/metabase/issues/10377

Are you sure the emails are not a cache from somewhere?
Have you checked the mail server log to confirm that Metabase is sending the mail at that time?

5

Hi @flamber,
I am having the same problem. I archived a pulse that was sending notifications to Slack channel. But even after archiving the Slack channel gets the alert.
Is there any solution that I can already try?

Metabase version : 0.38.4

Thanks & Regards
Nishya

6

@Nishya Are you having problems with Pulses or Alerts? It's two different things, but they share a lot of the same underlying structure.
When you archive a question, then it should remove the Pulse/Alert automatically.
Otherwise, try unarchiving the question and then remove the Pulse/Alert manually.
Though, it would be interesting to figure out what went wrong, so we can make sure that this is fixed.
Please post "Diagnostic Info" from Admin > Troubleshooting.