FFAStrans forum

I swear, I'm not picking on you guys!

I found that one of my workflows is always saving workfolders regardless of the state of either checkbox on the maintenance tab. The HDD on my FFAStrans machine filled up over the weekend because the attached workflow's working directory had grown to 300Gb. It did have "keep only failed jobs" checked, so I unchecked it, deleted the files and figured I found the problem. Today I noticed the working directory had more folders in it. I've copied the workflow, checked and unchecked both boxes, reset the workflow and rebooted the machine and the behavior persists.

Hey man....are you picking on us?!?!?

Does it happen to all your workflow or is it just this one?

-steinar

Just this one. I went through all of the workflow properties after I cleaned out the HDD and that one was the only one that had either box checked. I poked around a bit in the job logs and noticed something. All the other workflow logs have similar file structure with three directories, finished, sys, workflows, and a .json and full_log.json file. The logs associated with this workflow are missing the full_log.json and have additional tmp and log directories. This particular workflow is one of the oldest, has it kept some pre 1.0 function that can't be turned off now?

Can you please send a couple of the logs?

Hi crispyjones,

I think I know the reason for this behavior: Can you please not set s_source to nothing? Just remove it and see if it helps.

-steinar

AHA! This is all starting to make sense. That choice was a result of a discussion with @emcodem about ending a workflow branch without reporting it to the webui. Removing the s_source line does fix it and keeps the job file from being saved, though I do get the extra line reported to the webui. I also tried the other solution of setting a conditional node with "dispel" checked and that also resulted in an unwanted save of the job file.