How Do You Send a Tableau Subscription Immediately?

Tableau’s Server subscription test uses Schedules → select the schedule → Actions → Run Now. Review the subscriptions assigned to that schedule before running it; the action may affect more than the corrected sales email.

The individual-subscription workaround is explicitly for Tableau Server. It creates a schedule dedicated to the subscription, then runs that schedule. The article says there is no individual subscription Run Now button.

Do not carry that Server workaround over to Tableau Cloud. A Cloud reading copy can be downloaded and delivered through an approved route, but that does not test the native subscription’s email process. ATRS runs its own report job and connects to Tableau Cloud only.

The Excel options include tab names, workbook passwords, file properties and custom output names. Excel Data Only adds placement in a template worksheet, starting row/column or next available position, selected totals, reusable styles and column data types/custom formats.

That can give finance a corrected workbook ready for reconciliation, with recognizable tabs and the required date or currency formats. Open the resulting file and check the actual cells; exporting again does not guarantee that the source correction or reporting period is right.

A package schedule can deliver several attachments, combine Excel outputs, merge PDFs or ZIP the reports. Keep its report-level and package-level exception behavior with the job.

Date/time suffixes distinguish output files, and configured ZIP/password or PGP protection can protect delivery. Files & Folders tasks can merge existing workbooks or adjust workbook password, read-only and summary properties. Use these options when the extra report needs the same preparation as the regular one, rather than rebuilding the file manually.

An extra run uses the saved configuration at the time it executes. A relative date rule such as last week may select a different period when run later. Check its resolved dates rather than assuming Execute resends the original attachment.

For a historical replacement or a smaller audience, prepare a separate approved configuration with those values. Avoid temporarily changing a shared production schedule while another operator or recurring run may use it.

A new execution also does not prove that a prerequisite refresh has completed. If the reporting process depends on a separate readiness workflow, establish that readiness before requesting the report.

Follow the ATRS execution guide. This example uses an ordinary single-report schedule. Replace 101 with its actual UniqueId, use your ATRS HTTPS address and keep the bearer token on a backend that authorizes the reporting request.

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

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

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

Save the returned ExecutionId and monitor within a defined time limit. Parse the JSON-encoded ResultJson: Completed can still contain Result=false. Check the resulting report and destination evidence before presenting the extra delivery as successful.

Use the on-demand path deliberately. ExecuteScheduleOnTimeAsync follows the scheduled-time path and advances NextRun after completion; it should not replace the on-demand call when preserving the recurrence matters.

ExecuteScheduleAsync uses the stored report settings. This payload does not provide a new reporting period or recipient list, return the attachment bytes, or execute a native Tableau subscription. A direct report execution also does not establish that a separate readiness workflow has completed.

If submission times out, inspect execution activity and destination evidence before retrying. Work may already have started. Reconcile an uncertain run so the application does not send the replacement twice.