EDIT: Also have a look in Settings > Admin > Troubleshooting. You should be able to see the pulse (both the test and scheduled) and click details.
EDIT 2: Actually it looks like 0.31.3 was released a few hours ago, which adds Pulse logging to Troubleshooting - haven’t tested, just looked at the code.
I don’t think there’s a 0.31.3 image for EB. It seems like the version was created to help troubleshoot issues. It hasn’t been officially announced.
But it will be part of 0.32, when it’s released.
Have you gone through the timezone troubleshooting guide?
I confirmed that it uses UTC on both the container and host. Most days the pulse slack appears at the expected time. Some days it doesn’t appear. It’s worth noting that some of the queries average 50 seconds. I’ve not found anything suspicious in the logs.
Make sure you’re using the latest version 0.31.2
If pulses used to work, but suddenly stopped sending, then it might be a problem with a stale database connection - try killing all database connections or restarting Metabase.
I feel like I may have a similar issue and am on the current 0.31.2 release too.
On Tuesday I had setup a new daily Pulse to be sent at 8 AM and yesterday and today I didn’t receive a message (although sending the Test email of the Pulse did work fine and I know the SMTP configuration is all up and running fine).
I also have the Report Timezone setting in the General configuration area set to US/Pacific in Metabase.
I’ve reviewed those two Github Issues as well. What I can do is try and restart Metabase later tonight and see if the Pulse runs correctly tomorrow at 8 AM which might indicate our issue is the “stale database connection” situation.
Just to report back on my experience. I forgot to restart the Metabase service last night so I still didn’t get my expected 8 AM Pulse. Once I remembered to do so about 40 minutes (shortly after 9 AM) I updated the Pulse time to go out at 10 AM so I could more quickly see if things would work, then went ahead and restarted the Metabase service and waited.
I just received the Pulse so the issue seems to be fixed by restarting the Metabase service so hopefully you guys can figure out a long term fix for that issue since that’s a pretty core function that should work reliably for the system.
Also…would it be difficult to make it so users could have more flexibility regarding the times the Pulses go out? I hadn’t noticed till today but because the times can only be set in 1-hour increments it caused a longer wait time for my test since I couldn’t just set the time at 9:30 AM or whatever increment was closest.
I’ve upvoted that other feature request you shared. Hopefully the 0.32 release helps out (or at least gives us more info to troubleshoot things further and help you guys to find the long-term solution).
One thing I’m also going to give a shot (based on the 3846 issue you shared) is the Alert feature for Questions which I haven’t even noticed/tried out before. Looks to be quite similar to the Pulses (so it may have the same underlying issue requiring the restart of the Metabase service described in this thread) but I think it’s also another useful feature to know about since it seems to have a similar, but different use case.
From the documentation:
It’s a really common thing to keep tabs on a metric over time, and to want to be alerted when it goes above or below a specific value, or goal. To set up a goal-based alert in Metabase, all you need to do is create a time series question and add a goal line to it in the visualization settings, then click on the “Get alerts about this” option in the new top-right menu. You can also get goal alerts when you create a progress bar question.
Another situation where you might want to get alerts is when you have a question that returns rows in a table that match a certain condition. It might not usually return results, but you want to know when it does. As an example, maybe you have a question that returns all the bad reviews users have given your product in the past 24 hours. Hopefully that question doesn’t normally have any results, but you can set up an alert on it and tell Metabase to let you know if there are any bad reviews for you to look at.
This is still happening to us in May 2020.
On version v0.35.3.
Using the docker container version.
No errors in logs, pulse just doesn’t send after the first time.
I’m happy to get on a screenshare if you have never been able to reproduce.