Why Is the Tableau Subscribe Option Missing?

Content and credentials. Recipients need View and Download Image/PDF permissions. A source requiring an interactive database sign-in needs a supported unattended credential setup. A missing or expired OAuth credential can also prevent subscription. See Tableau Cloud troubleshooting.

Embedded views. On Tableau Server, restricted trusted-authentication tickets hide Subscribe and Alert buttons. This is a specific authentication behavior, not a rule for every embedded dashboard. Ask the portal owner to review subscription access guidance against the direct-view result.

Server configuration. The administrator should check SMTP and event notification setup, server and site subscription settings, and available enabled subscription schedules. See Server subscription setup and Server troubleshooting. These native Server checks are separate from ATRS, which supports Tableau Cloud only.

A missing frequency. If the dialog opens but When Data Refreshes is unavailable, inspect the data connection. The native option requires an eligible published-extract connection; live connections, multiple extracts and Bridge refreshes have restrictions. A Bridge-dependent update is not established by an unrelated extract refresh. Use the Cloud troubleshooting guide above.

Subscribing colleagues. Adding other users requires workbook ownership, administrative authority or project leadership with an appropriate site role. Their content access still matters. Native subscriptions send PNG, PDF or both. Save a Custom View for filters you need retained. See Tableau’s subscription instructions.

The Tableau account guide explains method-specific connection fields. Follow the Single Schedule guide for report inputs, timing, destinations and testing. The linked account still needs the required Tableau access and export permissions; the ATRS service needs access to its templates and delivery locations.

Both ATRS Excel modes produce XLSX files. The Excel output guide covers worksheet names, workbook passwords and file properties. Data Only adds template placement at a specified or next available row and column, selected row or column totals, reusable styling and typed column formats for dates, numbers and text. Check any existing formulas and template areas in the delivered workbook.

A Package Schedule can deliver multiple report attachments, ZIP them or merge PDF or Excel outputs. Test the final combined file as well as each report. Choose custom filenames and date/time suffixes that distinguish the reporting periods.

Use the Email destination guide for message and recipient settings. If the report is embedded in the body, an attachment is not included by default; select Include Attachment when required. HTML report embedding requires SMTP. Sending and receiving mail limits still apply.

If delivery depends on an external load or extract update, define and test that dependency in the reporting sequence. Moving the send time later is not proof that the intended period’s data is ready.

Use your ATRS HTTPS base address and keep the bearer token on the backend. This example runs an ordinary single-report schedule. Replace 101 with its actual UniqueId. Configure and test its report, period, output and recipients in ATRS first.

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

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Sales portal"
}

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

Save the returned ExecutionId with the portal request. Poll the status within a defined time limit and parse the JSON-encoded ResultJson. Completed can still contain Result=false; inspect the result and error details, then check the resulting file and destination.

The execution request runs saved settings. It does not supply a new recipient, reporting period or format, and it does not return the exported file itself. For packages, use the actual stored identifier and documented package schedule type.

Calling a report directly does not run a separate event parent’s conditions or tasks. Use the tested execution path that includes any required readiness checks. After an uncertain response, reconcile the execution and destination before submitting again, to avoid duplicate deliveries.

This is a separate ATRS delivery action; it does not restore Tableau’s native control or grant the linked account additional rights. See the ATRS Developer Hub for authentication and operation details.