How Do You Send Tableau Reports After Data Refresh, Including Bridge?

Follow the Tableau subscription workflow. Open the published view, choose Watch → Subscriptions and select When Data Refreshes where the connection qualifies. Save a custom view when filters must be retained, and check the received business date and totals.

Tableau’s troubleshooting guide identifies Bridge extract refreshes, multiple extract refreshes and live connections as reasons the frequency may be unavailable. With mixed connections, the trigger can follow a published extract without waiting for the Bridge connection.

An available refresh trigger therefore needs to match the source update the report depends on. A separate business approval or another source finishing may still be required before the figures should be distributed.

Tableau’s Bridge alert guidance confirms that refresh-initiated subscription emails are unsupported for Bridge extract sources. Failure alerts help the data owner investigate; an absence of alerts does not by itself prove that today’s extract is ready.

An external reporting-ready record should identify the source and close date and be written only after the required completion checks. A marker produced when the warehouse finishes is premature if Bridge has yet to update the extract.

Use a fresh record or file for the intended close, and define what happens after it is processed. A matching condition left in place can be found again. Test repeated signals and recovery so a delayed update does not produce duplicate morning emails.

A later fixed-time subscription is still an option when the business accepts that timing risk and monitors it. Describe it as a timed delivery, rather than a guarantee that every prerequisite has completed.

The Event-Based Schedule guide documents file/database conditions and execution order. Choose ALL when every selected condition must hold. For matching database records, use the documented detection and processed-record approach to prevent repeated execution. Ensure the scheduling service can access the condition source.

The General Custom Tasks guide documents the refresh target and completion wait. Confirm supported behavior in the installed version. A simple pause adds elapsed time; it does not check that an extract completed successfully.

For finance, Excel and Excel Data Only outputs offer worksheet names, passwords, file properties and naming. Data Only adds template worksheet placement, starting row/column or next available position, selected totals, reusable styles and column data types/custom formats.

Package schedules can combine Excel outputs or PDFs, send separate attachments or ZIP the files. Date/time suffixes help distinguish closes; configured ZIP encryption or PGP can protect delivery. Files & Folders tasks can merge existing Excel files or adjust workbook password, read-only and summary properties. Build Excel Workbook creates a workbook from database queries as a separate task.

Keep the required templates and locations available to the service, use the current Office prerequisites and open the delivered workbook during acceptance. Formatting and successful email delivery do not establish that the figures belong to the right close.

Use the ATRS execution guide. This request runs an existing ordinary single-report schedule after the application has established readiness. Replace 101 with the actual UniqueId and use your ATRS HTTPS address. Keep the token on an authorized backend.

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

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Stock close application"
}

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

Save ExecutionId with the source completion and close date. Monitor within a defined time limit and parse the JSON-encoded ResultJson; Completed can still contain Result=false. Check the produced files and destinations before marking the close’s reporting complete.

The request uses the stored report inputs and destinations. It does not supply a new close date, create a refresh task or install a Bridge monitoring hook. If an ATRS event workflow owns prerequisite checks or tasks, directly executing its child report does not establish that those separate steps ran.

Reconcile a repeated readiness signal or uncertain response with earlier executions and destination evidence before submitting again. Keep durable business history in the application so recovery can distinguish a missing report from an already-delivered copy.