I have a simple macro to activate an app at 6am so when I wake up, that's the app that's right there in front of me, because I want that to be my focus right away.
But I'm getting this every morning when I wake up:
2023-10-11 06:00:20 Action 13998113 timeout exceeded. Macro “Activate Todoist” cancelled (while executing Activate Todoist).
The macro works when I test it, but I'm wondering if the issue is that my screen and computer go to sleep and that makes it not work? If so, how can I go around it?
Do I use the Wake Screen action and would that be enough?
Maybe you could try two macros:
Macro 1:
6am: activate Macro 2
Macro 2:
Trigger on wake
Activate Todoist
Diable this macro
I just did a test with this:
It indeed worked. But then I got these messages, I don't know if they are important/relevant:
2023-10-11 09:54:14 Execute macro “Activate Todoist copy” from trigger Editor
2023-10-11 09:54:16 Running application query took a while (4232 us)
2023-10-11 09:55:59 Execute macro “Activate Todoist copy” from trigger At 8:56 AM every day
2023-10-11 09:56:00 Running application query took a while (3043 us)
2023-10-11 09:56:00 GetProcessForPID(41567) failed with -600 for <KBMRunningApplication “Todoist” <0x600003435560> pid=41567 bid=com.todoist.mac.Todoist abht>, using cached version```
What's your thought process here?
Macro 1 makes the computer wake up and then Macro 2 activates Todoist?
If so, wouldn't my new macro do the same when I use the Wake Screen?
I was thinking that it would activate Todoist the first time after 6am that you wake your mac manually, and no time thereafter until the following day.
No, my idea is that I want it to switch to Todoist before I wake up.
But I see what you mean. I can do that as well, since I will have to wake it up anyway so when I do, it activates Todoist. Good solution as well. Thanks!
1 Like
Actually, it won't work the way I just described, because then that would trigger it every time it goes to sleep and I wake it up.
I will test my new macro and see how that goes tomorrow.
Just giving it a few seconds to fully wake in case there's some delay/lag. Let's see how that goes...
Not sure whether you're referring to your initial idea or mine, but in mine, the crucial part is disabling macro 2 until 6am the following day.
Mine. When I said "I can do that as well, since I will have to wake it up anyway so when I do, it activates Todoist"
So in your case, running Macro 1 at 6am would wake the computer?
I will test mine tomorrow and see how it goes. If it works, I don't need 2 macros. If not, I will try yours. Thanks
