Hey @ronald,
Please post actual testable macros and not just images.
Finicky little details hide in macros that are not deducible via images and/or prose, and those are often key to solving a given problem.
The pictures you've shown are virtually meaningless, because the entire macro is not described – nor is there a downloadable, fully visualizable, testable macro file.
Even if you had created a proper image of the entire macro there would still be some of those finicky details hiding behind closed doors...
Note that Keyboard Maestro will accept variable names in the legacy variable format:
%VariableName%
Personally I wish @peternlewis would sunset that feature, because it periodically causes head bashing against the wall problems for users who either don't understand the difference between variables and text-tokens or inadvertently use a token name as a variable name and get very unexpected results.
If Peter jumps in I imagine he'll say: "Changing that would break some people's macros, so ixnay...", although this is one of those things (imo) where the minimal pain for a few users would be worth it.
In any case – I vehemently harp on this point:
<soapbox on>
NEVER, EVER use token notation as text-variable-notation.
I.e. never, ever use %VariableName% when you mean %Variable%VariableName%.
If you ever do this it almost certainly will come back to bite you at some point, and you might well waste hours or days trying to troubleshoot an easily avoidable problem.
Also – if you use the legacy notation you cannot ever be certain at a glance whether a string bracketed with percent signs is a token or a variable – while If you take my advice then you will always know at a glance whether you're dealing with a token or a variable.
I learned this from hard experience...
</soapbox off>
Take Care,
Chris
(Keyboard Maestro Moderator)