1 of 1 people found this helpful
I've had that issue a few times as well. For me it had to do with the Refresh Option I had configured on the server. Found this article about it for you to review.
Hopefully this will help out.
There is nothing wrong. Read the information that Jeffrey provided, that will help you figure out what you need to do. My server is set up to Balanced, 5 minutes. It originally was set up to Refresh More Often but I wanted to have some caching so the 5 minutes is the most my top developers/users were willing to compromise.
1 of 2 people found this helpful
The thing is, Tableau is NOT a real-time reporting application and that needs to be remembered.
A user pulls up a workbook and the Tableau Server grabs the data and presents it on the screen. Its job is done. It doesn't monitor the data source for changes so it cannot know when the data changes. This is why the workbook doesn't update suddenly when the data source is updated when a workbook is being displayed. In order to "tell" the workbook to pull new data the user must tell Tableau to do so by clicking the Refresh icon . Tableau will then re-query the data source and update the workbook. Imagine if one was looking at workbook, analyzing some marks when the screen would suddenly freeze and be unresponsive until the suddenly new data was being downloaded! In the real world not all workbooks run at sub-five second refreshes plus the constantly changing data would be highly troublesome & annoying for in-situation analysis.
Now, in the case of presenting the user will the freshest, newest data available when they open a workbook on the Tableau Server then, yes, Refresh more often is what you want. You'll lose the benefit of caching for other workbooks that aren't refreshed as often so it is a trade-off.