Here you go: Move to Inspiration Folder.kmmacros (20.2 KB)
Your macro works flawlessly for me. That is, I cannot reproduce the error.
Yes, they are all in Dropbox! Weird.
I can reproduce the problem ~50% of the time (right now) when Dropbox is on and 0% of the time when Dropbox is off.
OK, this seems to point clearly towards Dropbox. But I don’t understand why it isn’t happening when you do the same in the Finder (without KM macro). However, I don’t know the underlying code of KM’s move action. Maybe @peternlewis has an idea.
Especially if you are on Sierra, have you tried to
- unlink/relink Dropbox from the folder, as proposed above? (maybe throw in an OS restart in-between)
- update Dropbox by using a freshly downloaded installer?
I have an identical macro that uses that path above as the MoveLocation variable. When I run this macro, KM consistently tells me it can’t move the file because something already exists in that location.
When KM tells you that, it is usually true. I’m assuming you mean the message “File action failed because destination already exists…”
The 2nd part of that message tells you the exact path that is responsible for the error. Check that and check also the exact path composition in your macro. Sometimes an accidentally wrong path composition in the move action can lead to that result. (For example a missing last path component, so that KM tries to copy always the parent folder.)
But this is not the case with the macro you have posted, as said, it works fine here. And I get “File action failed because destination already exists…” only when the file indeed exists at the destination. So, this is probably a separate problem.
Are you using the current KM version? (I’m asking because IIRC there was a change with the path parameter of the Move action, but I don’t remember in which version.)