Tableau Cloud Help

A scheduled refresh can fail for a variety of reasons. As a data source owner, it's important to be aware of these refresh failures so that you can troubleshoot any issues and minimize gaps in data freshness.

If enabled by your site admin, you receive alerts about refresh failures for all of the data sources that you own. When refreshes for your data sources are facilitated by Bridge refresh or Bridge legacy schedules, the type of alerts you receive, when you receive them, and the alerts that you can configure differ from other Tableau alerts.

How you receive Bridge alerts

Bridge job failure notifications are delivered through Tableau's Unified Notification Platform, the same platform that powers your other Tableau notifications. Previously, Bridge sent these notifications by email only. Now, alerts about Bridge job failures—such as client disconnection, extract refresh failures, prep flow failures, and virtual connection failures—appear alongside your other Tableau notifications, in addition to email.

Bridge alerts are sent to the same audience as the email alerts: site admins and the data source owners.

No additional setup is required to receive these notifications. Make sure the Tableau checkbox is selected in your general notification preferences.

Differences with Bridge alerts

• Timeout refresh failure emails are sent when the timeout limit is exceeded. Unlike refreshes that run directly on Tableau Cloud, Bridge refreshes timeout after 24 hours (default). However, a timeout limit for refreshes can be increased (or decreased) through each Bridge client by a site admin. For more information, see Change the Bridge Client Settings.

• Notifications for Bridge-related refresh issues are sent to specific recipients depending on the failure type:

  • RAS failures: These alerts relate to a Refresh after Schedule (RAS) failure, meaning the job was successfully sent to the Bridge client but failed during or after processing on the client machine. Notifications are sent only to the data source owner. Site admins do not receive these notifications.

    • Refresh job failure: When an extract refresh fails for reasons other than those listed below (this is the catch-all for failures that occur once the job is with the client).
    • Bridge client is not running: When an upcoming scheduled refresh can't start because the client linked to the data source is not running.
    • Incomplete refresh: When a scheduled refresh hasn't completed after a specified amount of time.

  • Edge pool failures: These alerts relate to an edge pool failure, meaning the scheduled refresh job failed to run before it could be sent to the Bridge client due to issues with the pool capacity or client availability. These notifications are sent to the data source owner and the site admin.

    • Bridge pool at capacity: When extract refreshes can’t run because the pool is at capacity.
    • No clients in Bridge pool: When extract refreshes can’t run because there are no clients in the pool.

• For a particular data source, Tableau Cloud sends email about the first five consecutive refresh-related failures (i.e., refresh failures, alerts because the client is not running, or alerts because the refresh hasn't completed yet) on the first day. If the data source continues to have refresh issues after the first day, Tableau Cloud sends one email per day.

• A data source owner can receive up to 10 emails, one email per data source with active and consecutive refresh issues, in one day. The time period of one day is 24 hours starting at the time of the first refresh issue.

• Data refresh-initiated Subscription emails are not supported for views or workbooks that rely on Bridge extract data sources to keep data fresh. For more information, see Missing subscription emails.

Configure pooling

Extract refreshes can fail because of issues with the Bridge pool and load balancing. Site admins can configure and manage pooling for Bridge clients by adding a new pool or modifying the pooling capacity. For more information, see Configure Pools and Manage the size of the Bridge pool.

Stop receiving alerts when a client is not running

By default, Tableau Cloud is configured to notify data source owners when scheduled refreshes can't start because the Bridge client linked to the data source is not running.

There are two primary reasons why you might be receiving this email:

• The computer where the client is running from is not on.

• An extract data source continues to be associated with a client that is no longer in use.

If any of these reasons apply to your situation:

• Confirm whether the Bridge client is running, and

• If you're a site admin, delete unused clients from the site. If you're not a site admin, you can delete the data source from the client. For more information, see Scheduled refreshes appear to be running outside of schedule:.