Tableau Server has several built in time limits for process times and query executions. These limits can keep long running queries from monopolizing Tableau Server resources. Desired long running tasks may be prematurely capped by these timeouts. Error messages will warn that these timeouts have been exceeded. They can be seen in Desktop, on Server and while using
tabcmd. These include:
-
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 (30.000 seconds) was exceeded. -
Vizql::Error: Timeout error
Code: 999
Details:
Timeout communicating with server: execution expired -
Operation cancelled.
The session has exceeded the 30s limit -
HTTP request failed (400)
-
Cannot connect to Tableau Server. Please check the server name and port and try again.
When publishing a workbook, refreshing an extract or viewing a workbook on Tableau Server, there are two main timeout settings to be aware of. These two settings are the following:
-
gateway.timeout:Â Gateway.timeout covers the length of any action on Tableau Server, such as publishing a workbook with a large external file or extract.
-
vizqlserver.querylimit: Vizqlserver.querylimit specifically covers the queries executed to return views or populate extracts.
The gateway.timeout and vizqlserver.querylimit values are in seconds with these default values: gateway.timeout = 1800 and vizqlserver.querylimit = 30. Consult with a database administrator to determine the best timeouts for your environment. If the vizqlserver.querylimit is being increased above 1800 seconds, be sure to increase the gateway.timeout accordingly with the command ‘tabadmin set gateway.timeout NNNN’ where NNNN is the number of seconds.
For a detailed listing of other Tableau Server parameters, see the "Reconfiguring the Server" section in the Tableau Server Administration Guide.