TABLEAU QUESTIONS

What Scheduling Options Do Tableau Subscriptions Provide?

Monday’s management update is easy to put on a weekly schedule. Finance’s close is different: selected business dates and a company closure no longer fit the same simple pattern.

Advanced Tableau Report Scheduler (ATRS) can keep those reporting dates in a maintained calendar, alongside the Tableau Cloud report and its delivery.

THE DIRECT ANSWER Choose the recurrence for your regular update
REQUIREMENTS AND LIMITATIONS Decide when a business calendar is needed
END-USER WORKFLOWS Put the finance-close dates into ATRS
DEVELOPER AND API WORKFLOWS Request an extra report without rebuilding its calendar
CHOOSE YOUR NEXT STEP Choose the calendar you can maintain

THE DIRECT ANSWER Choose the recurrence for your regular update

The weekly management update has a familiar place in the diary. Managers expect it on Monday before their review, and an available Tableau subscription recurrence may cover that job well.

Finance then asks for its close report on two agreed business dates, with a company closure between them. Someone begins keeping reminders so the right file is exported on each day.

That is the point to put the actual close calendar beside the available scheduling choices. An ordinary recurrence is useful when it describes the dates the readers need; it becomes awkward when people must keep correcting it by hand.

ATRS custom calendars let the reporting owner select the required dates and maintain them with the delivery job. The calendar can follow finance’s close rather than ask finance to work around the nearest weekly pattern.

Native subscription frequencies and refresh conditions

Custom subscription schedules provide hourly, daily, weekly and monthly frequency families with the supported recurrence controls. Tableau Cloud uses custom schedules; Tableau Server administrators may provide fixed schedules or enable custom subscriptions.

Converting a Tableau Server site to custom subscriptions is permanent and converts existing subscribed fixed schedules. That is an administrator’s configuration decision.

Recipients, view/workbook scope, PNG/PDF output and the scheduling time zone remain part of the subscription setup. Report filters select the data period separately from execution time.

When Data Refreshes has published-extract eligibility conditions and Bridge restrictions. A calendar time or unrelated extract refresh does not establish completion of every source the report needs.

Further guidance: subscription setup guidance · Server custom-schedule settings

Start with the dates finance already uses. Ask which closures should prevent a run and whether the team chooses a replacement date when a close moves.

Native hourly, daily, weekly or monthly options may cover the management update. For individually selected dates and exceptions, an ATRS calendar can make the finance routine easier to maintain.

Keep the reporting period in the same conversation. The close report may contain the previous month even though it runs in the current one. Its report inputs select those figures; the calendar decides when the prepared file should be produced.

Custom dates, exceptions and report periods

Use the actual requested dates to decide whether a normal recurrence fits. A weekday pattern is different from the organization’s close calendar.

ATRS custom calendars provide individually selected dates and calendar exceptions. Excluding a date does not automatically move its run to another day; select an intended replacement separately where required.

Keep the previous-month or other reporting-period values in the report configuration. The calendar controls when the job executes, while those inputs control which figures it contains.

Data readiness is a separate dependency. Coordinate any required refresh or completion handoff before report production.

Further guidance: custom calendar guide · frequency settings

Prepare the finance report and a test destination first. Select its Tableau Cloud account and the period the close needs, then choose the output finance expects.

Create a named Custom Calendar in ATRS and select the agreed reporting dates. Apply it to the report schedule, with the execution time and delivery destination.

Open a test copy with finance and compare it with the close they are preparing. Then review the next selected date together, including how the company closure affects the plan.

Give someone ownership of maintaining future dates. Apply calendar changes to linked schedules and extend the calendar when needed, reviewing the jobs disabled at its end. The recurring preparation can then replace the reminders someone used to keep for every close.

ATRS keeps the execution calendar with the report schedule. The screenshot contains example settings; use your own reporting dates.

Calendar setup, updates and end dates

Create a named calendar under Custom Calendars, select the reporting dates, save it and apply it in the report schedule’s Schedule section. Set the execution time and intended destinations.

Use Update Schedules to apply calendar changes to linked jobs. Schedules using a calendar are disabled when it ends; extend the dates and review the offered re-enable option when continuing the calendar.

Check a representative reporting period and next selected run date with finance. Use the ATRS Scheduling Service configuration required for unattended execution.

Further guidance: ATRS Scheduling Service

Finance may need another copy between its normal dates. An application can request the saved ATRS job while the reporting team continues to maintain the report and calendar.

Choose the on-demand execution route for that extra copy rather than the scheduled-time operation that advances the next run.

API example: request an extra report between calendar dates

This example requests an existing ordinary single-report schedule. Replace 101 with its actual UniqueId, use your ATRS HTTPS address and keep the token on a backend that authorizes the finance request.

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

{"ScheduleType":"report","UniqueId":101,"RunBy":"API"}

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

Retain ExecutionId with the requested close. Monitor the run and parse the JSON-encoded ResultJson; Completed can contain Result=false. Confirm the expected report and destination.

ExecuteScheduleAsync is the on-demand route. ExecuteScheduleOnTimeAsync uses scheduled-time behavior and advances NextRun after completion. Choose the operation whose calendar effect is intended.

If an application maintains recurrence through SingleSchedule/Create or Update, follow the complete write contract, including valid dates and destinations to retain. A read response is not a complete write definition.

After an uncertain submission, reconcile the existing execution and destination before requesting another copy.

Further guidance: ATRS Developer Hub

What Scheduling Options Do Tableau Subscriptions Provide?

Choose the recurrence for your regular update

Ask what Monday at eight means

Decide when a business calendar is needed

Bring the real close diary

Put the finance-close dates into ATRS

Give the calendar an owner

Request an extra report without rebuilding its calendar

Make the extra copy easy to explain

Choose the calendar you can maintain

Contributors:

Christian Ofori-Boateng

About ChristianSteven Software