Deleting processed jobs
For each processed job, ABBYY FineReader Server creates an XmlResult and output files. These files will accumulate over time, clogging up the working folders and slowing down the program. To prevent this from happening, completed or failed jobs and their related files should be deleted from the working folders.
A job is deleted:
- automatically in the following cases (Web Services API only):
- when the client uses the synchronous ProcessFile or ProcessTicket methods
- when the client uses the asynchronous StartProcessFile or StartProcessTicket methods and then calls the GetJobResultEx method without the DoNotDeleteJob flag
- when the client uses the asynchronous StartProcessFile or StartProcessTicket methods and then calls the GetJobResult method
- manually, if the client explicitly calls the DeleteJob method
- automatically, 24 hours after the last access to its processing results
When a job is deleted, its XmlResult and output files may or may not be deleted, depending on the settings. The following four cases are possible:
- If the publishing of XmlResult files is not enabled, XmlResult files will still be published, but these XmlResult files will always be deleted together with their jobs.
- If the publishing of XmlResult files is enabled, XmlResult files will not be deleted.
- If a job is deleted using any of the methods listed in (a) and (b) above, its output files will also be deleted.
- If a job is deleted automatically 24 hours after the last access to its processing results, its output files will not be deleted.
- For jobs that have been created using a ticket with IsTemporary = TRUE: if a job is deleted automatically 24 hours after the last access to its processing results, its output files will be deleted.
See also
3/26/2024 1:49:49 PM