Error "Job timed out and cancelled" After Upgrading

Published: 27 Jun 2014
Last Modified Date: 04 Dec 2015


After you upgrade to Tableau Server 8.2.0, regardless of previous changes to the backgrounder.querylimit setting, background tasks might time out after approximately two hours, and the following error might appear in the background tasks view:
Job timed out and cancelled


Tableau Server 8.2.0


Option 1

Upgrade to Tableau Server 8.2.1 or a later version. For more information, see Upgrading Tableau Server in the Tableau Knowledge Base.

Option 2

Set the backgrounder.timeout_length_in_seconds to match or exceed the the value of the backgrounder.querylimit setting:
  1. On the computer running Tableau Server, open the Command Prompt window as an administrator and run one of the following commands:
    • On a 32-bit computer: cd "C:\Program Files\Tableau\Tableau Server\<version>\bin"
    • On a 64-bit computer: cd "C:\Program Files (x86)\Tableau\Tableau Server\<version>\bin"
  2. At the command prompt, run the following commands in order:
    • tabadmin stop 
    • tabadmin set backgrounder.timeout_length_in_seconds <seconds> 
    • tabadmin config
    • tabadmin start


Tableau Server 8.2.0 includes a backgrounder.timeout_length_in_seconds setting. The default value for this setting is 7300 seconds, and the value for this setting will override the backgrounder.querylimit values.

Additional Information

For more information about this issue, refer to the 8.2.1 Release Notes page.

In 8.2.0, there are now three configurable settings that govern backgrounder process time limits:
  1. backgrounder.querylimit limits the time that a single query can run. The default setting is 7200 seconds.
  2. backgrounder.timeout_length_in_seconds limits the time an entire background task can run. The default setting is 7300 seconds.
  3. backgrounder.timeout_tasks lists the tasks that the backgrounder.timeout_length_in_seconds limits. By default, these include: refresh_extracts, increment_extracts, subscription_notify, and single_subscription_notify.

In 8.2.1, backgrounder.timeout_length_in_seconds was replaced by backgrounder.extra_timeout_in_seconds.  The backgrounder.extra_timeout_in_seconds default of 1800 seconds is additional time on top of the backgrounder.querylimit number of seconds. 
Did this article resolve the issue?