What Scheduling Options Do Tableau Subscriptions Provide?

For a weekly management snapshot, start with the Tableau subscription scheduling options on your site. Open the published view, select Watch > Subscriptions, choose the view or workbook and the required snapshot format, then set the available frequency. On a site with custom schedules, define the recurrence instead of accepting a fixed schedule. The recipient’s configured time zone matters, so agree what “Monday at eight” means before saving.

For custom schedules, the native frequency families are hourly, daily, weekly and monthly, with recurrence details appropriate to each. Daily schedules can include selected weekdays and repeat intervals; monthly schedules can use dates or a weekday occurrence, such as the third Thursday. The available controls depend on the deployment and enabled schedule model.

Our analyst’s first question is whether the native recurrence already fits. Tableau’s custom scheduler can cover regular patterns, including hourly runs within a daily window. Its documentation shows a weekday, 09:00–17:00 example. Start with the choices offered by your site rather than assuming that a missing calendar option means subscriptions are unavailable.

On Tableau Server, a site may still use administrator-created fixed schedules. Enabling custom subscriptions requires server and site administration; the site conversion is permanent and converts existing subscribed fixed schedules. It is a configuration decision for the administrator, rather than something to change casually for one report.

Tableau also offers When Data Refreshes for a qualifying workbook using one extract on a published connection. That is a dependency on a supported refresh, not another name for a weekly clock. Bridge-backed sources need separate consideration; a selected schedule must not be treated as evidence that their refresh has finished.

Use Tableau’s subscription setup guidance and the Server custom-schedule settings to establish the native starting point. If the Monday image or PDF arrives on an acceptable cadence, there may be no need to replace it.

The finance close introduces a different problem: the reporting dates may be chosen individually and one of them may be a company closure. Compare the required dates and files, rather than deciding from the number of frequency options alone.

ATRS’s frequency settings and custom calendar guide describe separate controls for recurrence, selected dates and exceptions. For finance, the useful difference is keeping Tableau report delivery aligned with its maintained reporting calendar. It does not remove Tableau source permissions or turn a selected time into a delivery guarantee.

Suppose finance wants the September close report on 12 and 14 October, with no run on the company closure on 13 October. These dates are illustrative. First choose the authorized Tableau report and the PDF the finance manager needs; set its period to September before working on the calendar.

In ATRS, open Custom Calendars, create a named calendar and select the two reporting dates. Save it, then choose that calendar in the schedule’s Schedule section. Keep the time and reporting-period values explicit so someone reviewing the job can understand both when it runs and which figures it contains.

ATRS scheduling controls. The knowledgebase example’s dates are separate from the finance scenario described here.

Add the required email or file destination and preview a representative output at a controlled destination. Then review the next intended date. Skipping the closure in this example leaves 14 October as the next selected run; it does not automatically move a skipped job to another day.

Calendar maintenance matters after setup. When you change selected dates, use Update Schedules so linked jobs receive the changes. Without that action they retain the older calendar information. Schedules using a calendar are disabled when it ends; add future dates and use the offered re-enable option when extending it.

This replaces the analyst’s repeated calendar reminders and manual export dates with one maintained configuration. The analyst still owns the reporting period and the calendar’s future dates. Configure the ATRS Scheduling Service for the intended unattended execution environment.

An application may need to administer subscriptions or ask for an extra close report. Keep those responsibilities separate: changing a recurring definition affects future runs, while requesting an execution asks for a particular report now. The application should authorize either action before it reaches the reporting service.

Tableau’s REST subscription methods use different schedule models for Server and Cloud. Server subscriptions refer to an existing schedule; Cloud subscription requests define a frequency. Use the documented deployment-specific body and API version instead of copying the same payload between them. For an application that only manages native subscriptions, that API is a reasonable fit.

For ATRS, keep the maintained calendar in ATRS and use the ATRS Developer Hub for the documented schedule and execution operations. An application-requested run should not be presented as proof that the normal calendar has been changed. Likewise, do not assume a direct request automatically applies every rule used by the recurring scheduler.

In the finance example, an approved request for a replacement September report should record the intended period, job and destination. Track that execution separately from the next calendar run. If the request times out, investigate the run history before trying again so an uncertain response does not produce duplicate report emails.

See Tableau’s subscription API reference for the native request structures. That keeps a calendar change reviewable and an exceptional execution traceable.

Use a native subscription when its available recurrence and PNG/PDF output satisfy the reporting need. Give Advanced Tableau Report Scheduler a closer look when selected dates, closures and maintained exceptions are part of the recurring job. The difference becomes clear with one real calendar, rather than a list of hypothetical scheduling features.

Bring the next reporting period, its chosen run dates and a representative delivered file to the evaluation. Include a closure and the date after it, then confirm the behavior you expect before relying on the schedule.

See how ATRS handles your Tableau reporting calendar

Planning a calendar-based reporting job? Share the guide with the colleagues who will review deployment, licensing and the report’s operational requirements.

Download the ATRS Internal Evaluation Guide