Skip to content

FAQ and Glossary

Short answers to common Flow Scheduler questions, and the terms used across these pages.

FAQ

Do I need the Tableau Data Management add-on?

No. The Flow Scheduler schedules and runs Tableau Prep flows without it.

Which Tableau products does it support?

Tableau Server only.

Does it use the schedules I already have in Tableau?

No. Flow Scheduler schedules are stored in the Flow Scheduler, and Flow Scheduler admins create them on Admin > Schedules. You can import schedules and tasks from Tableau to start with. See Schedules and Import Tasks from Tableau.

Can one flow have several schedules?

Yes. Each task is one flow on one schedule, so a flow can have several tasks. Tasks belong to one Tableau site.

Which time zone do schedules use?

The Tableau server's time zone. The schedule dialog shows it as server time and previews upcoming firings in your local time. See Schedules.

Does task priority change the order in Tableau's queue?

No. Priority orders submissions only within one schedule's slot. Tableau's own queue does not see it.

What happens to runs when the Flow Scheduler restarts?

Flows already running on Tableau Server keep running and are picked up again. For each task, one scheduled run missed in the last 60 minutes runs as a catch-up run, unless the next scheduled run is within 4 hours. A chain that was running is marked failed; run it again.

What happens while Tableau Server is down?

Scheduled runs are held as SERVER_DOWN and start when Tableau Server answers again, unless the next scheduled run is within 4 hours. A manual run is not held; it fails with START_FAILED.

What can users do while the Flow Scheduler service is stopped?

The web interface still opens, but tasks cannot be created and runs cannot be started. A page or banner says the service is not available.

What happens to API calls when the Flow Scheduler is switched off?

Calls to /fss/v1 and /fss/backup fail until it is switched on again. See REST API.

How many nodes can run in high availability?

Two or more. One node is the leader and runs the schedules; the others are standbys. All nodes share one external PostgreSQL database. See High Availability.

How long is run history kept?

Indefinitely by default. You can turn on a purge of runs older than 180 days; it runs only while a recent full backup exists. See Configuration Reference.

Does the Flow Scheduler backup protect all of MetaMiner?

No. It covers the Flow Scheduler schema and the node's configuration files only. Keep your normal database and server backups. See Backup and Restore.

Can I automate the Flow Scheduler from scripts?

Yes, through the REST API with an API client token. See REST API.

Glossary

API client
A named caller of the REST API with its own token and access level. Managed in MetaMiner Administrator (MMA). See Manage API Clients.
Catch-up run
A run that replaces a missed or held scheduled run, for example after a Flow Scheduler restart. Shown with trigger Catch-up.
Coalesced run
A run recorded as COALESCED because Tableau refused a duplicate of a run already in progress for the same flow. Not a failure.
Environment
A Tableau Server connected to MetaMiner in MMA. It must also be enabled for the Flow Scheduler. See Allowed Environments.
Flow Scheduler admin
A Tableau user listed in MMA under Tools > FSS Configuration... > Admins. Sees the Admin area of the web interface.
Held run
A scheduled run waiting as SERVER_DOWN because Tableau Server is unreachable.
Leader
In high availability, the node that holds the lease in the shared database. Only the leader fires schedules, tracks runs and sends e-mail.
Linked task (chain)
A sequence of tasks run as one; each step starts when the previous one finishes. See Chains.
Output steps
The output steps of a Prep flow that a task or run writes.
Per-node setting
A setting set on each node and never copied to other nodes, such as the node id or the backup settings.
Preferred node
The node starred on Admin > HA / Nodes. Leadership returns to it after it has been healthy for a while.
Run
One execution of a flow, task or chain, with a status in Run History. See Run History.
Run Now
Starting a flow or task immediately, outside its schedule.
Schedule
A recurring time pattern stored in the Flow Scheduler (hourly, daily, weekly or monthly), in the Tableau server's time zone.
Shared setting
In high availability, a setting changed once on the preferred node and taken by the other nodes at their next Flow Scheduler restart.
Site
A Tableau site. You work on one site at a time in the web interface.
Standby
In high availability, a node that serves the web interface and waits to take over as leader.
Stop on failure
The chain step option Stop remaining tasks if this step fails.
Task
One flow on one schedule, with its priority, output steps, run mode and parameters. See Tasks.