Tableau Refresh, Export and Delivery Automation

Run Tableau Reports After the Right Data Is Ready

Use ATRS for Tableau refresh, export and delivery automation when your reports depend on a completed data load. Connect the load’s completion signal to an extract refresh and the report that follows.

Start from a defined file or database signal.

Set the refresh action and completion wait.

Keep refresh and report production in one configured job.

A Run Time Does Not Tell You the Data Is Ready

A report can arrive on time while showing yesterday’s figures. Define what must be true before it runs, then make that condition part of the reporting job.

The Load Has Finished

Choose a signal your upstream process produces after its work is complete. A completion record should identify the load it represents.

The Extract Has Refreshed

Starting a refresh and finishing it are different events. Decide how long the reporting job should wait for the refresh to complete.

The Report Covers the Right Period

A completed refresh does not choose the report’s date filters. Keep the intended business period explicit and check it in the exported file.

When Native Tableau Already Covers the Need

A Subscription After a Refresh

Use a Tableau subscription when a PNG/PDF email after an eligible extract refresh meets the requirement. Tableau’s “When Data Refreshes” option requires a workbook connected to one published extract. Recipients need View and Download Image/PDF permissions. Refresh-initiated subscriptions are not supported for extracts refreshed through Tableau Bridge.

Tableau subscription requirements

A Numeric Threshold Alert

Use a Tableau data-driven alert when the need is to notify people that a numeric threshold has been reached. Alerts can notify by email, in Tableau or through Slack; supported views need a continuous numeric axis.

Tableau data-driven alerts

Consider ATRS Tableau report scheduler when the reporting job must respond to an external readiness signal and coordinate actions before producing its files. Define the completion signal once, then use it to start the configured refresh and reporting steps.

Give Each Stage a Clear Job

1. Detect Readiness

An ATRS Event-Based Schedule can respond to a database record or file condition. Combine conditions with ANY when one is enough, or ALL when every condition must hold.

2. Request the Refresh

The released Refresh Tableau Datasource custom task can target workbooks or datasources using the selected Tableau account and item path.

3. Wait for Completion

Enable “Wait for refresh completion up to”, then enter the wait limit in seconds. A separate Wait/Pause action supplies an elapsed delay; a delay alone does not confirm that a refresh succeeded.

4. Export the Report

Select the configured report schedule as the event’s action. In Execution Flow, choose Custom Tasks → Schedules so the refresh task runs before report production.

Configuration: Event conditions and execution flow · Refresh and wait controls · Extract refresh release announcement.

Example: Produce Inventory After the Warehouse Load

Illustrative setup: the inventory team needs a PDF for the 14 October 2026 close. The warehouse load sometimes finishes late, so the job should start from a completion record instead of a fixed morning time.

Prepare One Report

Configure an Inventory Close report schedule with the 14 October business-date filter, PDF output and a restricted review folder. Select that existing schedule in an Event-Based Schedule, using a database condition that matches the completed load for that business date. If the event must be its only automatic trigger, disable the report schedule’s separate timed run; the event can still invoke it.

Put Refresh Before Export

Add a refresh task for the Warehouse Inventory datasource and enable its completion wait. Set Execution Flow to Custom Tasks → Schedules, so the refresh action comes before the Inventory Close report.

Run a New Test Load

Configure Detect New Records Only before the test record is created. After the warehouse update finishes, the data team writes a completion record with a unique load ID and business date. After a successful run, compare the PDF’s date and stock totals with the completed load, keeping its load ID with the test evidence.

START FREE TRIAL BOOK A DEMO

A checkmark clipboard, report page and magnifying glass illustrate reviewing a reporting job.

Decide What Happens When a Step Cannot Finish

The refresh completion wait is separate from the schedule timeout and retry settings. ATRS documents schedule timeouts in minutes and configurable retry counts and intervals. A wait limit by itself is not a guarantee that downstream delivery stops.

Test the exceptions as well as the successful run
Test case	Evidence to review
No readiness signal	Confirm the reporting step does not start early. Check which system owns the missing signal.
Refresh fails or exceeds its wait	Verify the recorded result and later-step behavior. If delivery must stop, demonstrate that configured outcome before release.
The same condition still matches	Check whether another run occurs. Define how a processed signal stops matching and how a legitimate retry is distinguished.
A retry follows a partial run	Inspect the review folder and job history. Decide whether recovery replaces a file, creates a version or requires operator review.

Use the exception cases above to confirm the required failure response in your installed ATRS version. Review exception handling alongside the refresh task and execution flow.

If you also need date rules, see calendar scheduling. For destinations and failed transfers, see delivery and recovery.

Trusted Report Automation for More Than 20 Years

ChristianSteven Software has helped organizations automate business intelligence reporting and delivery for more than two decades.

20+

Years of reporting automation experience

Nearly 5,000

Organizations helped worldwide

Countries with customer organizations

SOC 2 Type II

Independent assurance over security and operational controls

Visit Our Trust Center →

Technical Support

Get help with ATRS setup and configuration

Current Capabilities

Follow ATRS release announcements and product guides

Enhancements

Discuss your reporting requirements with the ATRS team

Not by itself. Have the upstream process provide a completion marker, or another agreed signal, after writing the data. Test the condition with a partial upload so the reporting job does not treat first appearance as readiness.

Detect New Records Only applies to records created after the event schedule is configured and fires once per record. Any Matching Records needs a suitably limited query and a processing step that stops completed work matching again. Neither setting alone guarantees exactly-once delivery after failures.

Yes. ATRS supports custom Hours of Operation for event-based schedules. Check that a readiness signal remains available until monitoring resumes; do not assume an event outside the window will automatically be queued and replayed.

The documented custom task runs Tableau extracts on demand. A live connection does not have the same extract-refresh step. Identify the connection and the upstream system that must finish before choosing the sequence.

Use an explicit supported signal written by the approval process, such as a qualifying database record. Define who can produce that signal and what approval it represents. An extract finishing is not evidence of business approval.

For unattended runs, configure the ATRS Windows Service on a supported, running Windows host. Use a Tableau account authorized for the selected content and give the service identity the source and destination access the job requires. Test the job under that service identity.