I have the need to read data from a supplied QR code that is a Base64 encoded *.PNG and part of the input data.
Unfortunately Exstream/StreamServe does not support this out of the box and I have to call an external tool for this.
I therefore create a temporary file that is placed in the %temp% folder with a unique name. Then I call the tool and read the extracted data from that output. That's quite quick and done in a few milliseconds, so it does not slow down the entire process.
In the "after job" script I delete this temporary file, as ti's only temporary, right?
It's all fine, until the application seems to remember that there has been a temporary file created and it starts complaining in the log about.
URI 'file:/C:/Users/…/AppData/Local/Temp/20251119141402123SjHd.png' modification detected.
And these entries pile up, cluttering my log. They seem to start right after a line of
StoryTeller job start with clearing options '0', job id '26132797', service '2589386970488', thread '11896', session '2589455383056'
and the list keeps growing until I restart the application.
I could just refuse to delete the temporary files by myself, as it looks as if Exstream wants to handle that by itself - but then the temporary files just pile up in the folder and don't get deleted.
It doesn't seem to happen always, there are days and weeks when there is no complaint (or it cures by itself) and others where i find literary hundreds of identical lines in the log for a single job, complaining of all deleted temp files from the previous jobs.
What could I miss?
