How Do You Send a Tableau Subscription Immediately?

To send a Tableau subscription immediately, first identify the report version and audience for the extra copy. Open the published Tableau view and confirm that the correction is present. Refreshing a browser is not the same as completing an extract refresh, and choosing a new time does not establish that the figures are ready.

For Tableau Server, an administrator can open Schedules, select the subscription schedule and choose Actions > Run Now. This is the documented subscription test route. Inspect which tasks belong to that schedule first: the selected schedule may cover more than the one email you have in mind. Tableau says its test snapshot should arrive within ten minutes; treat that as troubleshooting guidance, not a guaranteed arrival deadline.

On Tableau Cloud, do not assume the Server Schedules workaround or a per-subscription Send now button is available. Tableau’s subscription-specific workaround is documented for Server. General Run Now settings cover several job types and do not establish that a particular subscription has an individual execution action. For a Cloud report needed before its next run, an authorized download and approved email can provide the reading copy.

A manual PDF is separate from a subscription test: it shows that you can obtain and deliver that reading copy. It does not establish that the recurring subscription will render, address and send the same content. Keep that distinction visible when someone asks whether the “send now” test passed.

See Tableau’s Server subscription test and Cloud background-job guidance for the native controls and administration boundaries.

Tableau’s individual-subscription Run Now guidance describes the Server-only workaround. Use a schedule dedicated to that subscription when other subscriptions must not run with it.

The analyst needs one corrected PDF for the meeting, rather than a change to every future Monday email. Match the action to that scope before clicking Execute or Run Now. An urgent request is a reason to be precise about the recipient list, not a reason to skip it.

ATRS does not press a Tableau subscription button. It runs its own configured report export and delivery job. Choose it when repeated extra requests should reuse that maintained configuration; native subscriptions remain adequate when they already meet the reporting need.

For the corrected sales example, find the saved ATRS Single Schedule and inspect its source, reporting-period values, output and recipients. If the correction involves underlying data, establish that it is available in Tableau before running the job. A second execution with unchanged data can reproduce the same unwanted result.

Right-click the schedule and use Tools > Test when the first copy should go to a controlled test destination. Open the received PDF, check the correction and the reporting period, then review the production recipients. For the approved production copy, choose Execute from the schedule’s menu.

The ATRS schedule menu separates Preview, Execute and the Tools options.

The ATRS Single Schedule guide states that manual execution does not move the next run date and time. That lets the analyst keep Monday’s recurrence while requesting the extra copy. Verify the displayed next run after the request so the handoff is clear to the next operator.

Inspect the execution and destination results rather than sending a second copy because the first has not appeared immediately. Rendering, queuing and email handling all take time. If a file was produced but its destination failed, review that failure and any already-successful destinations before deciding what to repeat.

This is the recurring work ATRS takes over: the analyst reuses a maintained report configuration instead of selecting the view, exporting the PDF, naming it and composing the same message again. Approval of the audience and the corrected reporting values still belongs to the reporting owner.

A portal can offer an approved “send an extra copy” request while ATRS keeps the report and destination configuration. The portal should map the signed-in user to an allowed job; it should not accept an arbitrary schedule identifier or recipient list from the browser and trust it.

For an existing single-report schedule, the documented asynchronous operation returns an ExecutionId to track. The following request is illustrative: replace 101 with the intended job’s UniqueId, use the configured HTTPS installation address and keep the bearer token on the server.

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

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

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

Read ResultJson as well as Status. Completed can contain a failed result, and an absent result for an old queue entry is not success. Use bounded polling, retain the execution identifier with the original application request and confirm the expected destination file after a successful result.

Use the on-demand execution route deliberately. ExecuteScheduleOnTimeAsync follows the scheduled-time path and advances NextRun after completion; it is not interchangeable when the normal recurrence must remain. If a submission times out, reconcile history and the destination before retrying because the documented contract exposes no idempotency key.

The ATRS Developer Hub provides authentication and execution detail. Tableau’s native subscription API manages subscriptions. An extract-refresh request updates data; it does not replace the subscription’s rendering and email job.

Use the native action when you need to test or run the native subscription and understand its scope. Use a manual export for an occasional approved copy when that is all the reader needs. Consider Advanced Tableau Report Scheduler when extra report requests should reuse a maintained export-and-delivery job.

Try the corrected-sales example with a controlled destination: request one extra copy, inspect the file and confirm the next recurring run. That provides a concrete way to judge the reporting process without changing its normal cadence.

Explore ATRS Tableau report delivery and recovery

Evaluating on-demand report delivery? Share the guide with the colleagues who will review deployment, source access and the reporting job’s requirements.

Download the ATRS Internal Evaluation Guide