Address Timeouts When Publishing or Viewing

Product(s): Tableau Desktop, Tableau Server
Version(s): All
Last Modified Date: 16 Aug 2016

Article Note: This article is no longer actively maintained by Tableau. We continue to make it available because the information is still valuable, but some steps may vary due to product changes.

Tableau Server has several built-in time limits for processes and query executions. These limits can keep long running queries from monopolizing Tableau Server resources. However, a disadvantage is that long running tasks may be prematurely capped by these time limits. This article describes how to tell when this happens, and how to increase timeout levels.

Alerts that indicate when a time limit is exceeded

When time limits have been exceeded, alerts can appear in Tableau Desktop and Tableau Server, as well as at the command prompt after running a tabcmd command. Some examples include the following messages:

  • Vizql::Error: Unable to load workbook
    Code: 800
    Details: Errors occurred while trying to load the workbook "[path]". The load was not able to complete successfully. The query time resource limit (1800 seconds) was exceeded.
  • Vizql::Error: Timeout error
    Code: 999
    Details: Timeout communicating with server: execution expired
  • Operation canceled.
    The session has exceeded the 1800s limit.
  • HTTP request failed (400)
  • Cannot connect to Tableau Server. Please check the server name and port and try again.

Timeout settings

When publishing a workbook, refreshing an extract, or viewing a workbook on Tableau Server, the main timeout settings to be aware of include the following:

  • gateway.timeout: Covers the duration of any action on Tableau Server, such as publishing a workbook with a large external file or extract.

    Default value is 1800 seconds.

  • vizqlserver.querylimit: Covers specifically the queries executed to return views or populate extracts

    Default value is 1800 seconds.

Consult with a database administrator to determine the best timeout values for your environment. If you increase vizqlserver.querylimit, also increase the gateway.timeout accordingly, using the tabadmin set command:

tabadmin set gateway.timeout [NNNN]

Where [NNNN] is the number of seconds.

tabcmd global --timeout parameter

When you run tabcmd processes you can use the --timeout parameter to increase the number of seconds allowed for the server to complete processing the command. By default a process will time out after 30 seconds.

For information about these and other options you can configure, see tabadmin set Options and tabcmd Global Options in the Tableau Server Administrator Guide.

Configure gateway.timeout and vizqlserver.querylimit timeouts

The example here shows you how to increase the vizqlserver.querylimit timeout to 3600 seconds, or one hour.

Step 1

Sign in to the Tableau Server machine as an administrator or with the server Run As account.

Step 2

Complete these steps to open the Command Prompt as an administrator:

  1. Select to Start menu > All Programs > Accessories.
  2. Right-click Command Prompt and select Run as administrator.

Step 3 

Change to the Tableau Server bin directory using the appropriate path for your operating system and server version. For example:

  • 32-bit Windows: C:\Program Files\Tableau\Tableau Server\[version]\bin
  • 64-bit Windows: C:\Program Files (x86)\Tableau\Tableau Server\[version]\bin

Note: Replace [version] with the version of Tableau Server that you are running.

Step 4 

Run the following commands:

  • tabadmin stop
  • tabadmin set gateway.timeout 3600
  • tabadmin set vizqlserver.querylimit 3600
  • tabadmin configure
  • tabadmin start

Test the configuration settings

After Tableau Server is restarted, repeat the steps that led to the timeout error. If necessary, adjust the timeout limits again. If the limits are still reached, have a database administrator check the query that is being run. If everything seems to be properly configured on the database side, contact Tableau Support for assistance.


Alternate Search Terms:vizql, 400, cancelled, gateway, querylimit, execution expired, http, time out
Did this article resolve the issue?