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

The warehouse team keeps a stock dashboard on a wallboard. The browser reloads it regularly, so everyone assumes the figures are up to date. Then the manager opens the morning PDF and spots items that were dispatched yesterday.

Start with the data behind the view. A Tableau extract is a stored copy of data. The order system may have recorded those dispatches while the extract still holds the previous day’s stock. Asking the view to query that extract again cannot add records the extract has not received.

A live connection follows a different path: it queries the source instead of relying on that stored extract. Even then, cached query results can affect what the team sees. Tableau’s view refresh retrieves updated information from the configured source; the source itself still needs to contain the completed warehouse update.

The morning PDF is another part of the routine. It needs a process to generate and deliver it after the right data is available. ATRS can manage that file preparation and delivery, including a supported extract refresh beforehand when the workflow requires one.

The source data, the dashboard view and the delivered file each have a part to play in keeping the team informed.

For a wallboard that needs to display current figures, start with Tableau’s connection and refresh settings. Check that the source contains the new stock movements and, for an extract, that its refresh completed. Then check the report’s date and filters. A current source viewed for yesterday’s period can look like a failed refresh.

For the manager’s regular image or PDF, a native Tableau subscription may be enough. Where eligible, When Data Refreshes can send the snapshot after a scheduled extract refresh. That provides a useful native route when its format and refresh requirements fit.

ATRS adds value when the handoff needs more coordination. The manager might need a PDF by email, the warehouse analyst might need an Excel file, and a shared folder might need another copy. ATRS can maintain the report inputs, outputs and destinations along with the tasks that prepare the report.

It can also respond to a configured database or file condition when a warehouse load finishes at different times each day. Define what that signal means for this report: the file arriving or the load record appearing should represent the completed stock period the manager expects.

Build the ATRS job around the stock report the manager already uses. Select the Tableau account and report, set the supported business-date input, and choose the output and a test destination. Check that the selected period matches the completed warehouse load.

When ATRS needs to request a supported extract refresh, add the Refresh Tableau Datasource custom task before report generation. Choose the workbook or datasource, account and Item Path, then configure how long to wait for completion. Keep that refresh in the workflow that actually produces the file.

Run a controlled test after a known stock update. Open the received PDF and find the dispatched item from the warehouse system. Check the close date and total with the manager. The received file is the practical test of whether the whole handoff worked.

Then test what happens when the readiness signal is missing or the refresh fails or takes too long. Confirm the error response and whether delivery proceeds. Once those outcomes match the team’s reporting rules, enable the recurring workflow.

ATRS provides a Refresh Tableau Datasource task with account, Item Path and completion-wait controls.

The warehouse application may already know when the stock close is complete. It can request a tested ATRS report job at that point, leaving ATRS to prepare the PDF or workbook and deliver it.

Use the stock-close result as the reason to run the job. The wallboard’s page-load time only tells you about the display; it does not establish that the warehouse load has finished.

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

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Warehouse application"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-id>
Authorization: Bearer <ATRS-access-token>

The wallboard and the morning report serve the same team in different ways. Keep the dashboard querying the right data, and give the delivered file a workflow that uses the completed stock period.

Start with one stock report and one known update. Explore how ATRS can coordinate the required refresh, report preparation and delivery so the manager receives figures the team can use.

Explore ATRS refresh and report delivery