Yes, you right. I appreciate your patient.I cannot either reproduce it with a simple test folder with a simple python script.
So, now my question is: How does the clean up of the preview dialog works?
I can see that my script throws an error not on the matched files/folder, but on some sub folder/file.
Since the subfiles names are retrieved from the python script and not from the Hazel theFile parameter, could it be that the problem?
Maybe explaining my scenario a little bit more would be helpful. So these are the condition
- The folder's name must match this pattern "DD - ADD", where DD are two digits.
- The folder's subfiles/subfolder modification date has changed
- The folder musst contains a special file FF.txt. I check it with a python script.
- If yes, I run another python script as action
The action script:
- Get files from FF.txt
- Move them in another temporary folder (on Desktop)
- Zip the files and remove the temporary folder
A lot can go wrong in the action script, in fact sometime it throws an error and stop the whole process. I fix the problem quickly, usually a check on the files on FF.txt. Rerun manually the rule and check if the zip is created. Usually the zip is created, but the preview dialog keep showing the thrown error.
I'm having hard time debugging this problem, I can only imagine your difficulty in understanding it. So,
maybe a feature request would be to have the option to manually clean the preview dialog from errors (like a button)?