Speed up
- Thread starter db_123
- Start date
Done
Well. Depending on your phone. Delay between actions need to be longer for older (slower) phones and it can be short for new, faster phones. I am not sure what exactly you are clicking on in whatsapp so the only thing I could tell you probably don't need to wait 3 and 5s after first actions. It probably could be even less than a second of delay there. Also make sure there is no other - shorter way to do some things (for exemple writing can be replaced with ui interaction (paste) action with chosen text etc.)
Other thing you could try to do after launch whatsapp action is either:
Wait until trigger whatsapp launched, wait 1/2s
or
Create a loop with read screen content or check text on screen. Loop will stop as soon as it detects a word inside whatsapp that will mean its already opened and ready for next actions - thats generally the best way to reduce the delay between actions but you can't use it in some cases (when there is no one unique word that would mean macro can cancel delay and go to next actions)
Other thing you could try to do after launch whatsapp action is either:
Wait until trigger whatsapp launched, wait 1/2s
or
Create a loop with read screen content or check text on screen. Loop will stop as soon as it detects a word inside whatsapp that will mean its already opened and ready for next actions - thats generally the best way to reduce the delay between actions but you can't use it in some cases (when there is no one unique word that would mean macro can cancel delay and go to next actions)
Last edited:
dhj49er
Well-known member
Yes ...reduce the duration of the Wait actions.
As currently configured the Waits add up to 20 seconds.....time when MD is doing nothing and as @Brush has pointed out can be reduced and has suggested different methods to "speed up" the macro.
If you want to keep the existing macro.....start with the first wait and reduce it significantly. Then test the macro a several times and find the value where the next action runs every time. Too short a delay and the next action may not run correctly.
Once the first delay is set, move on to the next wait action and repeat the above. Do this for all the wait actions.
After completing the above you will have achieved the fastest that MD can successfully run the macro.
Is this time fast enough or still too slow?
If it's the latter look at @Brush post.
As others have hinted at your wait times can probably be reduced, but only you can experiment and find the fastest times that work reliably on your phone.