Skip to main content
Kofax

KTA received Canceled notification and for some reason second Kapow robot is spawned

3018466

Question / Problem: 

A KTA process will launch a Kapow robot. Somehow during robot’s run, KTA received Canceled notification and for some reason second Kapow robot is spawned.
Is this a timing issue and how it can be mitigated?

See, from the case:

21.png

Answer / Solution: 

Yes, it is a timing issue.
To change the amount of time used for the timeout, you should actually set the Target Duration value on the General tab of the activity’s settings.

Kapow Node General Settings.png

  Reference #5 and #6 here:
You also have the option of globally raising the limit by adjusting the “CoreWorkerActivityTimeoutIntervalInMinutes” value in the Core Worker config file (C:\Program Files\Kofax\TotalAgility\CoreWorkerService\Agility.Server.Core.WorkerService.exe.config).  Though it’s better to only use the Targeted Duration setting on the activities that you actually expect to run long.

Applies to:  

Product Version
KTA 7.5