-
1. Re: Alerts running at UTC
Matt Coles
May 22, 2019 2:42 PM
Hey Martin, I'm not sure I know of any timezone issues with Server from 2018.3 (that doesn't mean there isn't one, though). Best I can find is https://kb.tableau.com/articles/issue/tableau-server-time-zone-does-not-match-windows-server-time-zone?lang=en-us . As far as VizAlerts goes, it pulls the Run Next At time directly from what Tableau Server says in the schedules table in PostgreSQL, and that value is always in UTC. You can see the same dates in the \ops\vizalerts.state file.
Most likely, Tableau Server is not getting the right date/time from the system clock on the machine it's running on? Double check that the system clock is accurate?
-
2. Re: Alerts running at UTC
The system clock is accurate. It gets synchronized with the Domain Controller, which in turn uses a clock service to keep things synced. All servers and desktops, even company iPhones have exactly the same time.
BTW, the article you linked is outdated as it is calling to use tabadmin which is no longer used in 2018.3
-
3. Re: Alerts running at UTC
The strange thing is that the Schedule says 06:15, but the next run at on VizAlertsConfig says 11:15. So, that means that there is a discrepancy internally. Tableau server appears to be reading the timezone correctly from the server but vizalerts does not.
-
4. Re: Alerts running at UTC
Toby Erkson
May 22, 2019 3:20 PM
Have you investigated this?
schedules.display_schedules_in_client_timezone
Default value:
trueShows the "schedule frequency description" in the timezone of the user when true (uses the client browser timezone to calculate the "schedule frequency description")
-
5. Re: Alerts running at UTC
Just made the change, but I see no difference. The schedule still says 1:15 AM at the schedule settings, and 6:15 at the VizAlertsConfig viz.
-
6. Re: Alerts running at UTC
Matt Coles
May 23, 2019 3:30 PM
Here's a question: Are the standard subscriptions running at the correct time? If not, then I would escalate this to product support, as they're more likely to be aware of this issue and how to fix it than us. If typical subscriptions are going out on time, and it's just VizAlerts going out at the wrong time, then I'll dig in deeper with you. I have some workarounds that can help solve this problem for you, but I'm hesitant to suggest them, since it'd be far better to simply solve the underlying problem.
-
7. Re: Alerts running at UTC
If you mean the extract refreshes, yes, they are running at the scheduled time. Is only vizalerts schedules that are running at UTC instead of our local timezone.
-
8. Re: Alerts running at UTC
Matt Coles
May 23, 2019 3:42 PM
No, I mean the subscriptions feature that comes with Tableau Server, not extract refreshes. Subscriptions is the feature that VizAlerts piggybacks off of to do what it does. If you don't have any vizzes being emailed with Subscriptions, I'd try setting one up on a standard (non-VizAlerts) schedule, and see if it arrives on time.
-
9. Re: Alerts running at UTC
Oh, no. Since vizalerts we moved all subscriptions off TB own subscription service. I'll do that tomorrow when I get to the office. Thanks so far for all your help.
-
10. Re: Alerts running at UTC
Just created an 11 o'clock subscription, and it ran at 11AM. So the answer is yes, all subscriptions are running at the appointed time. So is definitively something with Vizalerts.
-
11. Re: Alerts running at UTC
1 of 1 people found this helpfulIs working now. Maybe it needed a full reset to take the configuration option.
-