Skip to main content
Kofax

The job was suspended as an activity timed out

Article # 3046421 - Page views: 149

Issue

A job suspends with the below error message.

The job was suspended as an activity timed out.

 

Cause

Core Worker activities have a 1-hour timeout in which they can be taken and completed.  For Transformation Server activities, this timeout is 2 hours.  If this threshold is exceeded, an activity will be reset to pending.  After a defined number of retries, if the activity still cannot be completed it will suspend with this error.

 

Additionally, if a target duration is configured at the activity level (purposefully or accidentally) this will override the server-level timeout.  For example, the below activity has a target duration of 1 minute.  This means if it is taken longer than 1 minute it will be reset to pending.

clipboard_ed31f2e8fe379c56caa2d3d6abd95ccdb.png

Solution

There are 2 options to resolve this error.

Option 1

Increase the Core Worker or Transformation Server taken activities timeout on a global level.  This can be done via the KTA Configuration Utility.

Core Worker

clipboard_e6ae92a5f3e7a786d20d61cd62d5fab71.png

Transformation Server

clipboard_e7f2e1b0007e94ccf60a7209818d2ae83.png

Option 2

Configure a Target Duration at the activity level to increase the taken timeout for a specific activity.

 

Additional Settings

The taken timeout interval also has a few other related settings.  These are explained below.

Reset Limit

By default, KTA will attempt to take and complete an activity 5 times before the job suspends with this error.  This value can be modified globally in System Settings -> General -> Auto Activity Reset Limit (left).  Or, at the activity level in the Execution settings (right).

clipboard_e1a07c62cb7c0fd953c65da3434bcb305.png

Polling Timeout

When the taken activity timeout has passed, it will not be reset automatically.  Both the Core Worker and Transformation Server poll at specified intervals to find taken activities that have exceeded the timeout.  Again, this setting is configurable via the KTA Configuration Utility.

clipboard_e7cb99021d881993e450cdc9d12cfa822.png

Note-Icon.png

NOTE: The Core Worker setting is in seconds whereas the Transformation Server setting is in minutes

Level of Complexity 

Moderate

 

Applies to  

Product Version Build Environment Hardware
KTA 7.5+      

References

KTA Help (here)

 

Article # 3046421