I’m posting on behalf of a client who is reviewing how their Laserfiche API Server handles temporary files. Specifically, we’re looking at the temp directory located at:
C:\ProgramData\Laserfiche\API Server\LFRepositoryAPI\Temp
Currently the folder keeps increasing in size, and they have confirmed that they are closing out the tasks/searches being performed to export data out of Laserfiche. The client nor myself have been able to find anything definitive, but I have seen some suggestions outside of Laserfiche sources (documentation, answers, etc.) that suggests this needs to be resolved manually or through the scripts being run.
We’re trying to confirm whether the Laserfiche API automatically cleans up this directory as part of its normal operation, or if these files persist unless manually removed. If the API does not handle cleanup on its own, we’d like to know whether the recommended approach is to clear this directory manually or incorporate cleanup logic into the scripts and processes that interact with the API.
If anyone has documentation, best practices, or real‑world experience with how the API manages this temp directory, your insight would be greatly appreciated.