Does Tableau Auto Refresh Also Refresh the Data and Send Reports?

Begin with the wallboard’s connection. If it queries a published extract, that extract is its data source. The warehouse may contain the completed overnight load while the extract still contains the previous close. Reloading the dashboard cannot supply rows the extract has not yet received.

Tableau’s view refresh guidance explains that the toolbar refresh clears cached results and retrieves information from the configured data source. That is useful when the view needs to query again. The extract refresh operation is the separate full or configured incremental update that changes the stored extract data.

Follow the source update, the displayed results and the delivered report as separate stages of the same reporting requirement.

For the wallboard example, compare the completed warehouse period with the extract’s successful update, then check the date selected in the report. This distinguishes an old extract from a current extract queried for yesterday’s figures. A page-load timestamp cannot tell you which of those situations applies.

Finally, locate the process that creates and sends the morning PDF. A browser reload extension repeats browser activity; it does not establish that this separate delivery ran. Once you know which stage is missing, change that stage rather than increasing the wallboard’s reload frequency.

Use the word refresh with its actual target. The following choices explain different behavior, so choose the one that advances the stage you identified.

Tableau Desktop’s automatic-update controls apply while an author changes a view or its filters. They do not create an unattended extract schedule or email delivery. Keep that authoring choice with the person composing the workbook.

A native subscription may provide the needed snapshot. Eligible workbooks using one extract on a published connection can offer When Data Refreshes; Bridge-refreshed extract sources do not support refresh-initiated subscription emails. Save required temporary filters as a Custom View when defining the subscription.

With a live connection there is no stored-extract step for that connection, but upstream readiness and report delivery still need owners. A working live query does not establish that a business approval occurred or a file was sent.

Keep the wallboard’s display requirement separate from the file the manager receives. Use Advanced Tableau Report Scheduler (ATRS) when the morning report needs maintained inputs, destinations and a configured sequence around source readiness.

Prepare one stock-close PDF with the linked Tableau account, actual report Item Path and supported business-date input. Use a test destination for the first output. The export account needs content access, export permissions and licensing; the ATRS service identity needs access to any condition source and delivery location.

If the selected sequence requires ATRS to request a supported extract refresh, the ATRS General Custom Tasks guide documents Refresh Tableau Datasource. Select the workbook or datasource, account and Item Path, then configure its completion wait. In an Event-Based Schedule, required custom tasks come before report schedules; keep independent timed runs from bypassing the condition.

Configure a supported extract task when it is needed for report production. The wallboard’s browser reload remains a separate viewing action.

Test the completed-load case, missing readiness and a failed or overdue refresh. A wait limit alone does not guarantee delivery stops; verify the required failure behavior in the installed configuration. Then open the PDF and compare its close date and totals with the completed source.

The ATRS Tableau refresh, export and delivery workflow provides the detailed sequencing guidance. For this example, the useful result is a manager’s file whose source and period are correct, while the wallboard continues to serve its separate display purpose.

Your application can offer “Produce the morning stock report” independently of the wallboard’s reload controls. Configure the report and its required dependencies in ATRS first. The application requests that saved job when the intended close is ready; it does not derive readiness from the dashboard’s page-load time.

The example below runs an existing ordinary single-report schedule. Replace 101 with its UniqueId, use the ATRS installation’s HTTPS address and keep the token on a backend that checks the user’s authority to request this report. Its saved period, output and destination determine the file.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json

{"ScheduleType":"report","UniqueId":101,"RunBy":"API"}

Keep the returned ExecutionId with the requested close date and the source-completion information your application uses. Follow that execution through GetExecutionStatus, parsing the JSON-encoded ResultJson as well as reading its status. Completed can contain Result=false.

When the execution succeeds, verify the PDF at the configured destination. Its figures and reporting date answer whether the manager received the intended close; a recently refreshed wallboard answers a different viewing question.

The public execution API does not control browser auto-refresh or provide a general operation to rebuild every kind of Tableau extract. Establish supported refresh and readiness steps in the configured workflow before exposing the application action. Repeating a report request cannot complete an unfinished warehouse load.

If a request response is lost, inspect the earlier execution and delivery before trying again. There is no documented idempotency key to prevent duplicate submissions. The ATRS Developer Hub covers authentication and the execution contracts for the reporting action.

Choose the operation for the stage that needs to change: an updated view, an updated extract or a delivered report. Give each stage an owner so the wallboard’s recent reload does not become the evidence used to release the morning PDF.

Evaluate the ATRS reporting workflow when the file-production and delivery sequence needs to be maintained alongside source dependencies. Keep display behavior with the viewing requirement.

Considering ATRS for reports that must use fresh data? Download the ATRS Internal Evaluation Guide to review source and reporting responsibilities with the data owner and operations team.

Download the ATRS Internal Evaluation Guide