Don't process rule if image is already in destination

I have a series of rules that are working well, especially when they spot a duplicate file and the throw away the dupes is setup.

However, there is a mid-step process where the image is run through a droplet and I would like the droplet not to run if the final destination folder has a duplicate of the file, as this results in the process running when not required and doubling or tripling usage. This comes about if the file is accidentally resent, and is rare, but it does happen.

The process is as follows - An image is received into a watchlist, renamed, and passes through a droplet to be emailed, before being moved to it's final destination folder on dropbox. If the image is a duplicate the throw away rule works well through each step until the droplet stage, which runs and resends the image via email even if it already exists in the final destination folder on dropbox. I believe this is because the folder used for the droplet is a pass through folder.

The last step (move to dropbox) works as intended first time around, and does not update the image in the final folder if it already exists, as the throw away dupes works well. It is the step before this I am stuck finding a solution for.

Is there a way I can tell the penultimate droplet rule not to process, and to delete the image, if a duplicate image already resides in the final destination (dropbox) folder?

At the moment, I think you'll either have to use a script or restructure things so the droplet only processes things at the destination. Does the droplet rename the file or move it itself?

Hi Mr Noodle,

Thanks for responding.

The droplet does not rename the file or move it. Hazel moves the file after the droplet has completed it's task, as there is one more step before all processing is completed.

Any suggestions would be greatly appreciated.

Again, I think either a script is needed or things need to be restructured, like having the droplet operate out of the final destination.