How Do You Schedule Tableau Data and Extract Refreshes?

The first decision is where North’s extract can be refreshed. Find the published workbook or data source and identify its original connection. Scheduling the workbook that displays a published data source is not a substitute for identifying the extract that actually needs updating.

In Tableau Cloud, select Explore, then All Workbooks or All Data Sources. Select the content and choose Actions > Refresh Extracts, then Schedule a Refresh. Choose the supported refresh type and recurrence. Cloud offers hourly, daily, weekly and monthly frequency families; the available intervals depend on that choice. For private-network data, follow the Bridge refresh schedule appropriate to the published source.

On Tableau Server, select the published content under Explore and choose Actions > Refresh Extracts. Select the available server schedule and refresh type, then Schedule Refresh. Server administrators create schedules on the Schedules page. Confirm your organization’s scheduling policy rather than creating a competing timetable.

Tableau Server’s scheduling dialog illustrates selecting the refresh schedule and type; Cloud’s scheduling controls differ.

For North, begin with one controlled overnight refresh and check the published source’s result. Use the approved source credentials for unattended access. The Server scheduling guidance explains how administrators control embedded credentials and failure notification. A successful interactive login alone does not establish that the unattended refresh can reach the database.

A recurrence should reflect when the source can provide useful new data. Refreshing every hour adds work without helping a report whose warehouse load finishes once each night. Conversely, an overnight refresh scheduled before that load finishes can complete successfully while still containing the previous close.

Full refresh is the default in the scheduling guidance. If Incremental is unavailable, inspect the extract’s authoring configuration and the selected content before assuming a permission fault. Do not switch methods solely to make the job faster; North still needs corrections to stock quantities to reach the report.

Keep the actual start, duration and outcome from the controlled run. Cloud documents resource limits for native refresh tasks, while Bridge has a different execution path. Investigate long-running jobs in the correct environment. Assign an owner who can distinguish a delayed start from a source error, and check how the next run behaves after recovery.

Keep the native refresh schedule when it meets North’s freshness requirement. The job changes when the warehouse load finishes at a variable time and operations needs a PDF only after the correct stock data is ready. That is a sequence to configure, rather than a reason to assume that a later email time proves completion.

The ATRS General Custom Tasks guide documents Refresh Tableau Datasource for a supported extract refresh. Choose Workbooks or Datasources, the linked Tableau account and the intended Item Path. Enable Wait for refresh completion up to with a suitable limit in seconds. The Tableau account must have the required authority for the selected operation.

Select the actual extract target and completion wait in ATRS; a separate elapsed pause does not establish success.

Prepare the stock report schedule with the approved North and business-date inputs, PDF output and a restricted review destination. If an Event-Based Schedule starts the job from warehouse readiness, choose Custom Tasks → Schedules so the required refresh task precedes report production. Keep any independent timed trigger from bypassing the intended readiness condition.

Test one completed load and compare the PDF’s date and totals with that source. Then test missing readiness, a failed refresh and an exceeded completion wait. Confirm the configured downstream failure behavior in the installed ATRS version; the wait limit itself is not a guarantee that delivery stops. The ATRS Tableau refresh, export and delivery workflow explains this handoff. Bridge completion needs its own verified path; do not infer an automatic Bridge integration from the presence of a refresh task.

An owned script is also a valid way to request a refresh. For a supported Tableau Server source, the tabcmd refreshextracts reference documents an administrator-or-owner operation using the published workbook or data source name. Establish an authorized session through your approved unattended authentication method before running this illustrative command:

tabcmd refreshextracts --project "Operations" --datasource "North Stock" --synchronous

Replace Operations and North Stock with the actual project and published source. The name is the one shown on the server, rather than the local file name used during publication. If the site administrator has disabled RunNow, resolve that policy with the administrator rather than treating repeated submissions as a fix.

The synchronous option waits on the Backgrounder job; it is not available for sources refreshed with Bridge. Handle the command result and refresh outcome before allowing a later export. Without a verified successful completion, a submitted request is only evidence that work was requested.

If an external scheduler repeats the script, keep its recurrence separate from any existing native schedule and avoid duplicate requests. Retain the source, intended load and outcome, then reconcile uncertain results before retrying. An application that owns export and delivery must also maintain the reporting period, authorized destination and recovery logic.

Start with the correct published extract, native scheduling path and approved source credentials. Check one useful refresh before increasing its frequency. For North, the evidence is the intended completed stock period and reconciled totals, not simply the presence of a schedule.

Consider the ATRS Tableau report scheduler when freshness is one stage of a maintained refresh-and-delivery job. Bring the source, completion signal and required report file so the team can test the entire result.

Considering ATRS for a recurring refresh-and-report sequence? Share the guide with the data owner and operations team to review deployment, access and the intended delivery outcome.

Download the ATRS Internal Evaluation Guide