There's no data that VizAlerts can use to determine if the alert has already been sent or not, unfortunately. However, there are other tricks you could employ.
- Is the extract it depends on local to the workbook, or is it a published data source? If the former, then the latest version of VizAlerts has a feature where you can schedule the alert to run when the extract refreshes, rather than on a time-based schedule.
- You could simply push the schedule back to when the extract was certain to have run by.
- You could build a calc to represent a datetime value for when the refresh last ran. For example, you could use an LOD calc against the data your alert viz is built on that simply looks for the maximum date value across all the records. If there is nothing from the last 24 hours, then you could assume that the data has not been refreshed yet, and the alert shouldn't be triggered.
- You could work with your admin to connect to the Tableau Server repository database directly, and blend information on extract refresh times into your Action calc. It'd be something like "if my alert condition is true, and the max successful refresh time for the extract was in the last hour, then send the alert".
Let me know if that helps.
I'll try these options out and report back. Thanks!
Hi Jose. If this answered your question, would you mark my answer as correct, please?
Sorry for the delay in answering.
I'm currently testing the refresh extract option to see if I get the results I want. I'm still trying to understand how the process work.
What I've done so far is set up the schedule and subscribed to the schedule on the viz I want and not the trigger viz. Is this correct?
The simplest way to test things out is to create a workbook with a single sheet on it and an extract that is refreshable. Publish it to Tableau Server and schedule it to refresh. Subscribe to the dashboard on the VizAlert schedule for Extract Refresh Success. Then, either wait for the extract to refresh, or kick it off manually. VizAlerts should send you an email if everything has been set up correctly. You can tweak things from there.
No luck so far.
I've subscribed to dashboard, refreshed the extract but didn't get an alert. I'll report back if I'm able to figure out what I'm doing wrong.
Ah, I forgot there was a bug with the manual extract refresh feature. Wait until the schedule runs naturally and it should work. Or you can apply the fix to the config workbook I provided here--then it will work with ad-hoc extract refreshes, too.
Thanks, Matt! I'm restarting our test server and will test it out when it comes back online.
I'll let you know how it turns out.
After some testing, it now looks like I was able to get it working.
Thanks, Matt Coles!