I’ve used KM for nearly 10 years in our operations and I find myself constantly adding short pauses (0.1 to 0.4) between steps in a dialog because they key presses are too fast (for example navigating an audio save dialog to select “mp3” in a pull down menu). That is, the dialog is not ready for the next keystroke. This seems very inefficient. Shouldn’t there be, or is there, a global pause? (Or am I just doing it wrong?) That is, slow down all actions or add a pause between all actions.
Truly "global" pauses can be done but would be even more inefficient -- why wait half a second for Set Variable "Local_x" to "Local_x + 1" when KM can do it in a millisecond?
Unfortunately, interfaces can be slow to respond and pauses are needed. And because the response time can vary even for different runs of the same macro, the optimal method is "Pause Until" so you macro waits just long enough but no longer. That's even more work, though
You'll have to find your own balance but, generally, the more often you use a macro the more effort you should put into optimising it. But for those times when it's enough to "put a 0.4s pause between all the following Actions" or "KM 'inserts text by typing' too quickly for this app" take a look at the "Set Action Delay" Action. Do read the "The Between Actions Delay..." paragraph very carefully, though!
