|
Component |
d.classify |
|---|---|
|
Version |
2.0, 3.0 |
|
Created on |
|
|
Last modified on |
No Workflow Applied |
|
Review status |
No Workflow Applied |
|
KB article number |
567967799 |
Summary
If the recognition quality of d.classify in d.capture batch is not satisfactory, it often helps to increase the recognition timeout.
If increasing the timeout does not achieve an improvement, the exact background must be analyzed at a technical level.
Important requirements
-
Administrative access to the server on which d.classify is installed. This is usually the d.capture batch server.
-
The Windows services must be restarted. You should therefore plan the adaptation with your team and those involved.
Solution
-
Open the configuration file for the d.classify service with a suitable text editor. Example path: D:\d3\d.classify\server\DClassifyStarter.exe.config
-
In the configuration file, search for the line <add key="max-thread-duration">. By default, the timeout is set to 30 seconds. We recommend adjusting the timeout up to 300 seconds: <add key="max-thread-duration" value="300"/>
-
Restart the d.classify service in the Windows services.
The increased timeout is effective immediately. You can test the new timeout directly.
If this measure does not sufficiently improve detection, a more detailed analysis by the edoc team is required. In this case, please open a ticket with all relevant information and examples in our customer portal.