Configure Pools

This topic describes how site admins can configure and manage pooling for Bridge clients. Pooling allows clients across the site to load balance data freshness tasks for data sources or virtual connections that connect to private network data.

The purpose of a pool is to distribute (or load balance) data freshness tasks among the available clients in a pool whose access is scoped to a domain within your private network. Pools map to domains, giving you the ability to dedicate pools to keeping specific data fresh and maintaining security by restricting access to protected domains in your private network. Pools map to domains via Routing Rules, giving you the ability to dedicate pools to keeping specific data fresh and maintaining security by restricting access to protected domains in your private network.

Tableau Cloud distributes tasks across available clients in a pool at random. If a client's connection drops mid-operation, in-progress tasks fail. However, live queries retry immediately on another client in the pool without requiring manual intervention.

Although the client in the pool that performs the data freshness task is chosen at random, if for whatever reason a client can no longer perform the task, the task is automatically rerouted to another available client in the pool to handle the task. There is no additional intervention required from you or your users to support or manage the pool of clients.

Pooling is optimized for keeping data sources or virtual connections that connect to data on one or more private networks fresh. Pooling support does not extend to data sources that use Bridge (legacy) schedules.

In general, pooling is optimized for the following situations:

  • Bridge is used as a critical service. If your organization requires that live query and scheduled refresh support must be available even if a client becomes unavailable.

  • Client is at capacity. If your existing site traffic exceeds the current capacity of the client.

  • Tableau Cloud-managed schedules for file-based data sources. Beginning with Bridge client version 2021.4.3, Bridge pools enable Bridge refresh schedules for file-based data sources.

  • Keeping data fresh on multiple private networks.

  • Virtual connections. (Requires Data Management) Bridge is required to refresh data in virtual connections that connect to private network data. For more information about virtual connections, see About Virtual Connections and Data Policies.

Before configuring the pool

Before you can configure a client pool for your site, review the following:

  • Clients must be installed and running. For more information about software and hardware, see Plan Your Bridge Deployment.
  • Clients are configured to run as a service. For more information, see Application versus Service mode.
  • The user authenticated into a client is a Tableau Cloud site admin. For more information about deploying Bridge, see Plan Your Bridge Deployment.
  • To keep virtual connections fresh, ensure all clients in the pool are running Bridge 2021.4 (or later).
  • To load balance file-based data sources, ensure the following:
    • All clients in the pool are running Bridge 2021.4.3 (or later).
    • References to file data must use the full UNC path that includes the server name or hostname. For more information, see About the Bridge Client.
    • File-based data sources are extract only.

Note about user roles

Only site admins, or users with either the Site Administrator or Site Administrator Creator role, can configure and maintain pooled clients. Regardless of the type of user authenticated into the client, only site admins can add new pools, add clients to a pool, remove clients from a pool, and monitor clients in a pool.

Note about refresh jobs

The Jobs page can show you the completed, in progress, pending, canceled, and suspended all Bridge refresh jobs that use Bridge refresh schedules. This includes refreshes for file-based and non-file based data sources. For more information, see About Bridge Refresh jobs. For more information about various ways you can monitor Bridge activity, see Monitor data freshness tasks.

Step 1: Ensure clients can connect to the site

In order for Bridge to work with your site, you must allow clients to authenticate to the site.

  1. Sign in to Tableau Cloud using your site admin credentials and go to the Settings page.

  2. Click the Authentication tab and validate that the Let clients automatically connect to this Tableau Cloud site check box under the Connected Clients heading is selected. For more information about this check box, see Access Sites from Connected Clients.

    Note: If enabled, the connected clients option must be enabled to support multi-factor authentication with Tableau authentication. If connected clients are disabled for your site, Bridge can only support Tableau username and password authentication.

Step 2: Configure a pool

Pools, which require Bridge 2021.4 (or later) clients, help route live query and extract refresh jobs to the appropriate private network. Use pools to access data distributed across multiple private networks, enable extract refreshes for file-based data sources, and to support data freshness tasks for virtual connections.

  1. On the Bridge tab, under Pooling, click the Add New Pool button.
  2. In the dialog box, enter a new pool name in the Pool text box and click Save.

After you have at least one pool configured, as part of the publishing process, Tableau Cloud associates certain data sources or virtual connections with Bridge and client pools automatically.

Step 3: Configure Routing Rules for your pools

Routing rules tell Tableau Cloud which pool should serve live queries and extract refreshes for a private network domain (or IP address) and, optionally, one or more projects. Manage these rules on Tableau Cloud in site Settings > Routing Rules. For detailed configuration steps, see Manage Routing Rules.

The total number of combined pools and routing rules in your organization may not exceed 100.

Routing basis

Routing decisions are made strictly on the basis of hostname or IP address and, when using Routing Rules, the project containing the data source or virtual connection. Connection strings and individual connection parameters are not evaluated or used for routing.

Rule types

  • Allow: Maps matching private network traffic to a designated named pool.

  • Block: Blocks Bridge connectivity to the specified domain across the entire site. Block rules take no pool assignment and apply site-wide (you cannot block a domain for only specific projects).

Shared domains across pools

Without project scoping, a domain maps to only one pool. With Routing Rules, multiple pools can share the same domain as long as each rule pairs the domain with a unique set of projects.

Example: Route the same domain to different pools

When multiple projects need to access the same underlying host using dedicated client resources:

  • Rule 1: Host database.myco.lan + Project A → routes to Pool A

  • Rule 2: Host database.myco.lan + Project B → routes to Pool B

Each rule pairs the host domain with a distinct project. Therefore, both pools can share the domain without conflicting.

Managing domain and IP specifications

When configuring routing rules, specify the server names or IP addresses used in the data source connection or virtual connection:

  • Exact domain name: Can be an FQDN or PQDN (e.g., mssql.myco.lan, fitness-challenge). Port numbers are not allowed.

  • Wildcards: Use a leading wildcard followed directly by a period to cover subdomains (e.g., *.myco.lan).

  • Exact IPv4 address: Literal IPv4 addresses (e.g., 192.168.0.50). IPv6 addresses are not supported.

  • Subnet ranges: Use CIDR notation to define IP ranges (e.g., 10.0.0.0/16).

Note: Do not use *.tableau.com in routing rules. The domain *.online.tableau.com is used for proxy filtering for outbound connections.

Routing rules syntax and guidelines

Use the following rules when specifying the domains and projects to route or restrict Bridge traffic:

  • The total combined count of pools and routing rules may not exceed 100.

  • Every domain and project combination must be unique; duplicate combinations cannot be saved.

  • The specified domain or IP must be accessible by all Bridge clients within the assigned pool.

  • Project-based routing evaluates the project containing the published data source or virtual connection, not the workbook or flow using it. Web-authored content is matched by domain only.

  • Ensure at least one named pool exists before creating an Allow rule. The Default Pool remains available for backward compatibility, but named pools are recommended.

  • An optional leading wildcard (*) includes all subdomains and must be followed directly by a period (*.myco.com).

  • Do not include port numbers. Exact domain names can be an FQDN or PQDN.

  • Domain entries support alphanumeric characters (A–Z, a–z, 0–9) and common symbols (- . * / @ # % & ( ) + = [ ] { } ; : " , < > ? | \).

Note: Do not use *.tableau.com in routing rules. The domain *.online.tableau.com is used for proxy filtering for outbound connections.

Scenario Description Example
Exact domain name Can either be an FQDN or PQDN. Port numbers are not allowed.

myco.com

marketing.myco.com

oracle.myco.com

Range of domain names Use an optional leading wildcard (*) to include all subdomains. The * must be followed directly by a period. *.myco.com
Exact IPv4 address Use an IPv4 literal (abbreviations are not allowed). IPv6 addresses are not allowed.

255.255.0.1

192.168.0.0

Range of IPv4 addresses Use CIDR subnet mask notation to include a range of IPv4 addresses. 255.255.0.1/16
Block rule Site-wide deny. Blocks Bridge connectivity to matching hosts across the entire site regardless of pool. Does not take a pool assignment. oracle.myco.com (Blocked)

Routing rules examples

Example 1: Database data

Suppose you want Bridge to:

  • Perform data freshness tasks for data located in data.lan and sqlserver.myco.lan.

  • Prevent data freshness tasks for data located in oracle.myco.lan.

To enable Bridge to support this scenario, set up the following rules in site Settings > Routing Rules:

Domain Rule Type Pool Project Result
*.lan Allow Pool A All Refreshes data in data.lan.
sqlserver.myco.lan Allow Pool B All Refreshes data in sqlserver.myco.lan
*.myco.lan Block (None - Site-wide) All Blocks data freshness tasks site-wide for *.myco.lan (including oracle.myco.lan), while sqlserver.myco.lan remains unblocked via its explicit Allow rule.

Example 2: File data

Suppose you have file data (\\fileserv.myco.lan\Shared\employees.csv). To enable Bridge access to this file share, create an Allow rule assigned to your target pool using one of the following domain patterns:

  • Option 1: *.lan

  • Option 2: *.myco.lan

  • Option 3: fileserv.myco.lan

Note: The host machine must permit network access to the shared folder, references must use the full UNC path, and file-based data sources support extract refreshes only.

Step 4: Add clients to a pool

Follow the procedure below to assign clients not already assigned to a pool.

Note: To support data freshness tasks for all data, ensure clients in the pool are running Bridge 2021.4 (or later).

  1. On the Bridge tab in the Unassigned Clients table, navigate to the client you want to assign to a pool and click Assign.
  2. In the Pool drop-down menu, select the pool you want to associate with the client.
  3. Repeat step 2 for each unassigned client you want to assign to a pool.

Troubleshoot pooling

Bridge Refresh jobs fail with one of the errors listed below.

The following errors can be seen on the Jobs page and the Background Tasks for Non Extracts admin view.

  • "errorID=NO_POOLED_AGENTS_ASSIGNED"

    This issue is specific to default pools and can occur for one of two reasons: 

    • When the server address or IP address of a data source does not match an active Routing Rule. This causes refresh jobs to route to the Default Pool where there may be no assigned clients. Ensure an Allow routing rule exists for the data source's domain and project, and that the rule points to an active pool.

    • When there are no clients in the default pool. To resolve this issue, add at least one Bridge 2020.2 (or later) client to the default pool. For more information, see Step 4: Add clients to a pool.
  • "errorID=NO_POOLED_AGENTS_ASSIGNED_NAMED_POOL"

    This issue can occur when there are no clients in the named pool. To resolve this issue, add at least one Bridge 2021.4 (or later) client to the named pool. For more information, see Step 4: Add clients to a pool.

  • "errorID=NO_AGENT_IN_POOL_SUPPORTS_REMOTE_EXTRACT_REFRESH"

    This issue can occur when a refresh job tries to run without at least one Bridge 2020.2 (or later) client in the pool. To resolve this issue, add at least one Bridge 2020.2 (or later) client to the pool. For more information, see Step 3: Configure Routing Rules for your pools.

  • "errorID=NO_POOLED_AGENTS_CONNECTED"

    This issue can occur when none of the clients in the pool are available to run data freshness tasks. For more information, see the Configure Pools section above.

  • "errorID=REMOTE_EXTRACT_REFRESH_ALL_AGENTS_BUSY" or "errorMessage: Maximum concurrency reached" in the client

    These issues can occur if the number of refresh jobs running at a given time exceeds the capacity of your client pool. To help resolve this issue, you can do the following: 

  • "errorID= AGENTS_IN_POOL_REQUIRE_UPGRADE"

    Beginning with Tableau 2021.4, this issue can occur when the clients in the pool need to be upgraded to Bridge 2021.4 (or later) in order to run data freshness tasks. For more information about upgrading clients, see Install Bridge.

  • Duplicate routing rules or unmatched project errors

    If queries fail to route or error out:

    • Duplicate rules: Verify that duplicate rules combining the exact same domain and project do not exist.

    • Project match: Verify the data source or virtual connection resides in the project specified by the rule. If content is moved to another project, update the rule accordingly.

    For more troubleshooting guidance, see Manage Routing Rules

Bridge clients are being signed out

This issue can happen if you deploy a large number of clients under the same Windows services account. When there are more than 10 clients running under one Windows services account, account security measures can cause clients to be logged out. For more information, see Windows services account.

Other potential pooling issues

When trying to diagnose issues related to pooling, consider reviewing the following log files for a client on the Bridge client machine: tabbridgeclijob_<process_id>, jprotocolserver_<process_id>, stdout_jprotocolserver_<process_id>. For more information, see Change the Bridge Client Settings.

Adding a new pool results in error, An internal system error occurred

Occurs if the total combined count of pools and routing rules exceeds the limit of 100.

Thanks for your feedback!Your feedback has been successfully submitted. Thank you!