Digitalize document activity creates massive amounts of "Magick" files

Help Activities
, ,
1

Hello everyone!

I’m having an issue that I have just discovered after processing a larger number of files (upwards of 10k PDF’s). My digitalize document activity is producing several “magick-…” files in a temporary folder. this is absolutely clotting my hard-drive since they seemingly dont get cleaned up after being used.

image
image1059×500 164 KB

Here is a small sample, they have over the course of three days clotted almost 120GB of space, so many rivers small so to speak.
I’m not sure why they started to appear now all of a sudden, especially since I haven’t touched the part of code that they are being produced in.
image
image1888×676 104 KB

Am I going about this wrong or is this some sort of bug?
Any help would be greatly appreciated!

2

Hi @theEmailRobot ,

Could you let us know from what date it was being produced ? And if there was any specific changes in the Environment or in the workflow before that date ?

3

Hello @supermanPunch

The earliest magick files I could find were from the 16th, on monday morning.
Looking back at my git workflow I can’t see I made any specific changes that day, I did put the robot into production with the workflow file that day however. But I had been testing it way before that on the same type of data, just from different input /output directories and havent seen any spikes in storage space.

4

@theEmailRobot ,

Was the testing done in separate environment or the same environment ? And was the Testing done using only Studio or Non-Production/Unattended robots as well?

5

Same environment, I know it’s not best practice what I’m doing but I have a “testing path” in my Xaml that just set’s a bool to true and that decides what config.json file to pull values from.
For the time being I’m not using orchestrator other than to build my own libraries, my robot is being deployed according to a windows schedule.
Another very simular program that has been in production for a few weeks has also started to produce these magick files I’ve just confirmed.

I do everything in the same environment and only using Studio, I have only one attended robot.

I did remember I set up a connection to Google Sheets on the 16th, but that was for a new project and the two that started producing the magick files doesn’t use anything connected to those activities from what I’m aware, not even sure that this information is relevant but it is something I did that day.

image
image1507×428 26.5 KB

6

I have put in a temporary solution while I keep searching for answers, but for now the robot has a simple function that cleans up all “magick-*” files from the folder in question right before program end.

Any further help or suggestions would be greatly appreciated. :smiley: