How Do You Schedule Tableau Data and Extract Refreshes?

Tableau Cloud. Refresh schedules offer hourly, daily, weekly and monthly frequency families. Full refresh is the default; incremental must be configured before publishing. Selecting full-only content can disable the incremental choice. Cloud also documents a two-hour refresh timeout. Review the applicable path and error before applying that limit to a Bridge job. See Cloud scheduling.

Private-network data. Bridge schedules rely on the clients, pools and source access maintained for the site. After publishing, the data source’s Extract Refreshes tab provides controls to add a refresh or change its frequency. Confirm the connection and credentials work unattended. See private-network refresh scheduling.

Tableau Server. Administrators create schedules on the Schedules page. Select the published content under Explore, choose Actions > Refresh Extracts, then the available schedule and refresh type. See Server scheduling. These native Server instructions are separate from ATRS, which supports Tableau Cloud only.

Native email after refresh. An eligible published-extract connection can support When Data Refreshes subscriptions. Bridge refreshes, live connections and multiple extracts have restrictions. If a mixed-source workbook offers the option, the triggering extract refresh does not establish that its Bridge update completed. See subscription troubleshooting.

The General Custom Tasks guide documents the refresh target and completion wait. A separate Wait/Pause adds elapsed time; that alone is not evidence that a refresh succeeded. Verify the failure and timeout behavior of the installed sequence rather than treating the wait value as an automatic stop rule.

The Event-Based Schedule guide describes file and database conditions and starting an existing schedule. Use ALL when every selected condition must hold. Define the period and completion evidence, and test repeat polling so one completed load does not generate unwanted repeat deliveries.

For Bridge-managed updates, verify the actual supported refresh and completion path. The presence of an ATRS refresh task does not establish a universal Bridge completion hook. If an external process owns the update, supply readiness evidence that covers the required extract and period.

The Tableau account needs access to the selected content and requested operations. The ATRS service needs access to condition sources, templates and destinations. Use the Single Schedule guide for report setup, and the Excel guide for workbook preparation. Check the actual attachment or saved file, including any merge, protection or template.

Use your ATRS HTTPS address and a backend-held bearer token. This example runs an ordinary single-report schedule. Replace 101 with its actual UniqueId. Configure its report, supported refresh tasks, output and destinations beforehand and test success, failure and timeout behavior.

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>

Retain the returned ExecutionId. Poll status within a defined time limit and parse the JSON-encoded ResultJson; Completed can contain Result=false. Inspect errors and verify the file’s period and destination before confirming readiness.

Executing a report directly does not run a separate event parent’s conditions or tasks. If the readiness check or refresh lives there, this direct request is not a substitute. Use the documented execution route for the tested job and its actual schedule type.

The request runs saved reporting settings. It does not define custom tasks in the payload or create a native Tableau refresh schedule, and its execution ID is not a Tableau refresh-job identifier. Native refresh administration follows Tableau’s supported configuration.

After an uncertain response, reconcile the earlier execution and destination before submitting another run to avoid duplicate reports. See the ATRS execution and monitoring guide.