Hazel trying to re-import the same photos over and over

Well, it turns out that Google has discontinued Picasa in favor of their (online) Photos app. So it looks like photos is my only option if I want it to run locally and also integrate with photostream, etc.

Perhaps I can explore the delay a little? Where exactly would I put that in Hazel? I don't mind slowing the import down to a snails pace if it means that it will work. I am not importing large quantities of photos - only the occasional batch of new photos as they are taken.

simonmason wrote:Probably time to switch back to Picasa. This is definitely more trouble than it is worth.

Just use the "Run shellscript" action. It's a clumsy workaround but given how flakey Photos is, any port in a storm, as they say.

Still trying to get this to work. The latest issue is that in addition to repeatedly trying to add the same files into the Photos library, Photos is now showing duplicates in it's library (but not on disk). I opened my laptop this morning and got to watch the series of events.

After a clean boot Photos loaded itself and reported that it had a duplicate photo. I clicked do not import and apply to all future imports and it finished. I then checked the Hazel view by folder and it said it was unable to import the folder in question. Then it tried again, photos popped up the duplicate import message again, and after saying don't import it finished. Now when I checked the Hazel view by folder it says that the folder is now imported.

In photos, the files in the folder in question now appear 16 times. I have not once clicked on the import duplicates in Photos. So somehow Photos is duplicating the images.

I am assuming Photos must provide some acknowledgement back to Hazel when it adds a photo - is there not a way that you can trap this to prevent Hazel from attempting to add the same photo over again and again? Even if it means coding around Photos issues? My photos library is not unusually big - in fact it appears based on other forums that it is exceptionally average. I am happy to run some other tests, even clear out my library and try adding from scratch. Thanks.

Code: Select all: 2016-05-22 08:05:37.585 hazelworker[752] Processing folder Current 2016-05-22 08:05:39.931 hazelworker[752] 2016-05-21: Rule Update Photos matched. 2016-05-22 08:05:51.054 hazelworker[752] Could not find album with specifier: Name: Current, Identifier: mLhLo0yWSHqYHs5ypIESqg, Type: 1 2016-05-22 08:05:51.054 hazelworker[752] [Error] Photos import failed: Could not add file /Volumes/SD/Photos/Current/2016-05-21 to Photos. 2016-05-22 08:05:51.101 hazelworker[752] Done processing folder Current 2016-05-22 08:05:52.480 hazelworker[781] ###main load address: 0x10c869000 2016-05-22 08:05:52.481 hazelworker[781] ###Noodle load address: 0x10c973000 2016-05-22 08:05:52.481 hazelworker[781] ###CK load address: 0x10c939000 2016-05-22 08:05:52.510 hazelworker[781] Processing folder Downloads 2016-05-22 08:05:54.540 hazelworker[781] Done processing folder Downloads 2016-05-22 08:06:07.610 hazelworker[785] ###main load address: 0x1098a2000 2016-05-22 08:06:07.612 hazelworker[785] ###Noodle load address: 0x1099b8000 2016-05-22 08:06:07.612 hazelworker[785] ###CK load address: 0x109979000 2016-05-22 08:06:07.631 hazelworker[785] Processing folder Trash 2016-05-22 08:06:08.785 hazelworker[785] Done processing folder Trash 2016-05-22 08:09:41.794 hazelworker[871] ###main load address: 0x106178000 2016-05-22 08:09:41.812 hazelworker[871] ###Noodle load address: 0x10628a000 2016-05-22 08:09:41.813 hazelworker[871] ###CK load address: 0x10624d000 2016-05-22 08:09:41.886 hazelworker[871] Processing folder Current 2016-05-22 08:09:44.071 hazelworker[871] 2016-05-21: Rule Update Photos matched. 2016-05-22 08:09:56.779 hazelworker[878] ###main load address: 0x105a4b000 2016-05-22 08:09:56.781 hazelworker[878] ###Noodle load address: 0x105b5d000 2016-05-22 08:09:56.781 hazelworker[878] ###CK load address: 0x105b21000 2016-05-22 08:09:56.816 hazelworker[878] Processing folder Downloads 2016-05-22 08:09:58.840 hazelworker[878] Done processing folder Downloads 2016-05-22 08:10:06.478 hazelworker[871] Done processing folder Current 2016-05-22 08:10:41.030 hazelworker[917] ###main load address: 0x100503000 2016-05-22 08:10:41.042 hazelworker[917] ###Noodle load address: 0x100614000 2016-05-22 08:10:41.042 hazelworker[917] ###CK load address: 0x1005da000 2016-05-22 08:10:41.349 hazelworker[917] Processing folder Current 2016-05-22 08:10:43.858 hazelworker[917] Done processing folder Current 2016-05-22 08:10:55.737 hazelworker[929] ###main load address: 0x10ddaf000 2016-05-22 08:10:55.745 hazelworker[929] ###Noodle load address: 0x10debb000 2016-05-22 08:10:55.745 hazelworker[929] ###CK load address: 0x10de83000 2016-05-22 08:10:55.838 hazelworker[929] Processing folder Downloads 2016-05-22 08:10:57.858 hazelworker[929] Done processing folder Downloads 2016-05-22 08:11:10.898 hazelworker[938] ###main load address: 0x1026e1000 2016-05-22 08:11:10.899 hazelworker[938] ###Noodle load address: 0x1027f2000 2016-05-22 08:11:10.899 hazelworker[938] ###CK load address: 0x1027b8000 2016-05-22 08:11:10.924 hazelworker[938] Processing folder Trash 2016-05-22 08:11:12.040 hazelworker[938] Done processing folder Trash

That error indicates maybe that the album you specified earlier was deleted and re-created? Try resetting the album in the rule again and see if that fixes things.

The albums are showing correctly in Hazel. Just to be safe I re-selected them. I did notice that when Photos was stuck on its duplicate screen then Hazel could not read the album information - so this could just be another timing issue.

I guess my question is simple at this point - it appears that Photos has issues that prevents the Hazel function from working. Are you aware of anyone with a reasonably size Photos library that has management to get this working?

It's a mix. Frankly, it's hard for me to work out a pattern of when it will work and when it won't. If you can find a suitable alternative photo app, I'd look into that as I don't consider Photos to be particular robust or mature at this point.

I can confirm that this is indeed an issue. When Picasa was sunset, and everyone moved to Google Photos, there were some loose ends. So far I haven't seen a script that can take on the mistakes Google left open. Perhaps if the data is treated via IFTTT first?