I'm dealing with the Big Sur known issue (by everyone but Apple, apparently) of my external drives randomly dropping off.
I've created a KM to email me when any of the four externals drop off. What I'd like is to customize the email to tell me which drive dropped off. I currently receive an email for each, and the redundancy is fine with me, but they're equally === uninformative.
Any way to capture to a variable the name of the drive which triggered the email?
EDIT: for this reply I'm using "partition" and "volume" interchangeably, since OSX handles partitions as mountpoints and calls them Volumes. FYI.
I don't think that survives stress testing. As there are two partitions (which appear as Volumes on the Mac) on each of 2 drives (so, 4 volumes, 2 drives) they always knock offline in pairs as this OS glitch only sets its sights on drives. KM is definitely detecting the individual drives (partitions) disconnecting, and thus sends two emails. The workflow you suggest fails as follows (I think… correct me please)…
Partitions A and B are sent offline together (it's always together)
KM kicks into action and starts processing /Volumes/A/ partition's disconnect and the Path Condition ifs...
IF » Path Condition » Nothing Exists » /Volumes/A/
Partition A is indeed offline so I get my variable set and get sent my email telling me that Partition A is offline. Cool cool cool.
IF » Path Condition » Nothing Exists » /Volumes/B/
Partition B is indeed offline so I get my variable set and get sent my email telling me that Partition B is offline. Cool cool cool.
KM kicks into action (again) and starts processing /Volumes/B/ partition's disconnect and the Path Condition ifs...
See what happens here?
I'd get at least a duplicate email for 2 volumes, and quadruple emails for 4 volumes going offline together.
When the macro executes, its %TriggerValue% token will hold the name of the volume (technically, the last path component, which will sometimes be slightly different to ensure uniqueness by the system).
I knew there would be something at the very base of it all, Peter doesn't spare these details. I just didn't know what to search for.
As for missing it on the info page, which I did review but only by scanning, I can only blame the oxy for my shoulder surgery. That's my story and I'm sticking with it.