Hi Shelly. As you might expect, we'll probably need some more information to help. Could you provide the following, please:
- Screenshot of the schedule in Tableau Server (both the Subscriptions tab and the Details tab--feel free to redact names and such). We'll need info from the top and bottom screenshots shown here
2. Second, please post the logs from the time that the alert was supposed to have run (be sure to redact sensitive info!). My guess is that this is a Schedule issue, however.
3. Ensure that the owner of the viz is the one who subscribed, if this is an Advanced Alert.
4. Make sure the subscription is on the View, rather than the Workbook:
find the screen below.
Yes, I have subscribed to the view and I am the owner and have subscribed myself.
I am baffled since the test_alert works, which means that something is wrong with the Alert setup, but I can't seem to figure it out.
Thanks Shelly. I'm a little confused, though--didn't you say the issue was with the daily schedule? Yet the screenshots appear to be of the hourly schedule. So I still need the Details page of the schedule (whichever the right one is), and the logs for when the alert was supposed to have run. I can't tell what the issue is with what you've provided so far...all I know is that it's something to do with your subscription, your Schedule, or how VizAlerts is recognizing the schedule.
we have three schedules, hourly, daily and 15min.
At this time we are having trouble with both.The subscription to any of the Alert (daily/hourly/15min) does not work.
Yet the test_alert works.
I will try to get the logs.
The test_alert comment working is good, certainly. That's what is telling me that the issue is most likely with your Schedule, since the test_alert method doesn't require a schedule at all. Sometimes it's because the schedule is set to run at minute intervals that prevent it from "running" at all. Sometimes it's because they're named in such a way that VizAlerts doesn't recognize them (I don't think that's the problem here though).
You have a VizAlert schedule named "Alerts - Hourly". Did you use the Cyrillic capital A when you created that VizAlert schedule?
If you are having a problem with that then try using a different VizAlert scheduling name trigger. I changed my schedule name in the SQL code of the configuration file, ...VizAlerts\config\vizalerts.yaml, to
... LOWER(sch.name) LIKE 'zalert_%' ...
This forces my VizAlerts to the bottom of the scheduling list & I don't have to content with odd character sets. This is my list of VizAlert schedules:
Why did you blank out all of the subscription schedule names? Now we can't see if there is a naming conflict.
I blanked the ones which are not relevant to VizAlerts.
We are using only 'Alerts - Daily' for VizAlerts, which is not blanked out (image 3)
Thanks Shelly. Everything you showed me is looking correctly set up so far...the only two things I can think of that would help troubleshoot more are:
(1) the logs from VizAlerts showing what happened at 1pm on any of the days that the schedule was to run on
(2) confirming that the subscription was created on the View and not the Workbook, as I showed in one of the screenshots I posted.
can you direct me to the location where I would get the VizAlerts logs?
here you go with the screen shot specifying that the subscription is done on the 'view'.
Well, that's good news, then--VizAlerts is processing it as expected. The reason you're not getting any email from it is because when it downloads the CSV data from the viz, it's empty--there's no data. So why then would you get an email when you do the test_alert comment on it, versus when it runs normally? That I don't know. Perhaps at 1pm on weekdays the data simply happens to be missing, and thus doesn't show in the viz? Your team would know better than we would, why that might be the case. I'd double check your filters.