That's not a macro it's an isolated action.
Macros contain many moving parts, and some of them are hidden. Sometimes those hidden bits are the key(s) to troubleshooting a problem.
So... It's generally best to post the simplest possible test macro that demonstrates the problem you're having, and when possible a macro that doesn't require specialized software to run.
The easier you make it for others to test your work the more likely you'll get timely and useful assistance.
It's a good practice to test and eyeball a benign result when working with shell scripts and things like KM's move, copy, and anything else that requires a path.
Download: Folder Trigger ⇢ Test.kmmacros (3.0 KB)
I've debugged more than a few problems and prevented quite a few disasters by following my own advice.
You should also have a kill-switch if you don't already: