Why Did My Tableau Subscription Email Fail or Not Arrive?

If your Tableau subscription email is not arriving, start with one expected occurrence. Record the report, recipient, scheduled time and time zone, then compare them with the subscription’s actual configuration. For the sales example, keep the missing manager’s address alongside a colleague’s successful copy so the administrator can compare the same update.

Check that the manager is included and still has View and Download Image/PDF access. Review whether Don’t send if view is empty was selected and whether the saved view was empty for that run. Expected suppression is different from failed delivery. Also confirm whether this was a scheduled subscription or a refresh-triggered one; a refresh request alone does not establish that an eligible subscription ran.

Ask a site administrator to inspect the matching subscription job. In Tableau Cloud, the Jobs page shows status, queue and run information; Task Details provides the failure, delay or cancellation context. A pending job is waiting to run. Creating more copies while it waits can make the eventual recovery confusing. See Tableau’s background-job guidance.

If the job completed but only one reader is missing the email, ask the mail administrator to trace that message using the recipient, subject and occurrence time. Check junk folders, quarantine and mailbox rules as part of that trace. These are investigation steps, not proof that filtering was the cause.

Correct the step that failed before changing the subscription or sending another copy. The analyst’s Monday update might be waiting, unable to render, suspended after repeated errors or already in the receiving system. Each condition requires different evidence.

Tableau documents stale or removed embedded credentials and temporary database unavailability as rendering causes. On Server, unusually complex views can also exceed the rendering timeout; investigate the recorded error before an administrator considers changing a server-wide threshold. Server subscription troubleshooting describes those conditions.

The Cloud troubleshooting guide gives five consecutive failures as the default suspension threshold. Fix the underlying cause, then have the owner or administrator resume the subscription. Resuming resets the failure count; its next evaluation occurs at the next scheduled time, rather than guaranteeing an immediate email. Follow the Cloud suspension and resume guidance.

For Tableau Cloud’s standard sending route, the mail team should check the current Tableau sending domain and IP requirements. A site using custom SMTP has a different set of required sender and IP values. Refer to Tableau’s current delivery requirements instead of copying an old allowlist into a new mail configuration.

If the sales update is produced by ATRS, investigate that job directly rather than changing an unrelated Tableau subscription. Open System Monitor > History View and locate the run. Expand the entry to review the report and destination results. One failed destination among successful destinations is recorded as Partial Success.

Review report generation, each destination and any retained output before choosing what to resend.

Use the ATRS History View guide to locate the failed handoff. If report generation failed, investigate the source and output first. If a file was produced but email failed, inspect that Email destination, its addresses and the selected sending account.

ATRS Email Log records SMTP messages; for Exchange or Office 365, check the sending account’s Sent Items folder. Review the receiving mail trace separately. The Email destination guide also cautions that changing displayed sender details can conflict with mail-server rules. Select a configured account authorized to send the message.

For Monday’s missing copy, first establish whether an earlier attempt already reached the receiving system. If a saved output is needed, snapshots must have been enabled and the original file must still be retained. Locate the correct period and use the chosen recovery procedure; enabling snapshots after the failure cannot recover a file that was never kept.

Review already-successful destinations before retrying. If the output must be regenerated, use the original reporting values so a recovery copy does not silently become today’s report. The ATRS delivery and recovery workflow explains retained-file recovery and the destination-specific decisions. This is where a Tableau report scheduler can consolidate recurring production and recovery work.

An internal application can lose track of a report even when the reporting service accepted its request. Preserve the application’s request reference, the chosen ATRS schedule and the returned ExecutionId together. A timeout while waiting for the initial response is an uncertain submission, not evidence that nothing ran.

For an ATRS asynchronous execution already submitted, query the documented status operation with its returned identifier. The request below illustrates that status check; it does not submit a replacement run. Use the configured HTTPS installation address and keep the bearer token on the application server.

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

Read ResultJson together with Status. Completed can contain a failed result, while missing result data for an old entry does not establish successful delivery. Poll within a defined time limit and retain the result needed for the application’s own reporting record. Then inspect the destination result and received output.

Before submitting again after an uncertain response, reconcile the execution history and destination. The documented contract does not provide an idempotency key that makes repeated execution requests automatically safe. Where a job has several destinations, choose recovery deliberately so the colleagues who received Monday’s update do not get unintended duplicates.

The ATRS Developer Hub covers the execution contract. Application tracking should connect the approved request to the result; it does not replace native Tableau job evidence when the failed delivery was a Tableau subscription.

For the missing Monday update, close the investigation with a received, opened report for the intended period. Record the failed step, the correction and which recipients were sent recovery copies. Confirm the next recurring run remains as intended, and give its owner enough information to recognize a repeat of the same failure.

Keep native Tableau subscriptions when they meet the reporting need and their administration provides the evidence you require. Consider ATRS when the recurring job needs maintained export settings, several destinations or a defined recovery process. Its own configured delivery route must still be verified through to the reader.

Review ATRS report delivery and recovery

Evaluating a more maintainable delivery process? Share the guide with the colleagues responsible for report production, mail administration and recovery.

Download the ATRS Internal Evaluation Guide