For the best, most useful help, please upload your macro .
You might find this macro helpful to identify and debug your macros when you get an error:
MACRO: Display Last KM Macro Error Ver 4 [Pub]
This macro also makes it easy to display the last N lines from the KM Engine Log.
This strongly suggests that it is an UI timing issue.
When you use a KM Action that issues some UI command, like Type a Keystroke or Select Menu, KM has no idea how long it will take the target app to respond. And so KM immediately goes on to the next KM Action.
I almost always put a very short delay (like 0.1 sec) after such an Action. Sometimes it takes longer.
When you step through the Macro using the KM Debugger, carefully observe how long it takes the App to respond to each of these Actions.
Please read:
Tip: How Do I Get The Best Answer in the Shortest Time?