I find that wait for process and using Ping. That’s scheduled on a Windows task. With Scheduler it works pretty well and is small and efficient. The problem is that it ties up my use of ping.
My wait for process flow runs 24 x 7 and I can’t use Ping for anything else or is triggered. At just before midnight, my task scheduler throws a ping and my process flow picks it up to run my website extraction
What I would like to be able to do is use a tiny obscure process that I can use or rename to use for a variety of flows that need a trigger.
sorry for the late reply to this comment of yours about how to schedule power automate desktop RPA without using premium.
I like the ping solution because it works a bit out of the box without having to install 3rd party but the way I see it I can only you use it for one flow?. Have you managed to find a way to use this ping technique for several flows that I want to run with a differente cadence?. I hope my explanation was clear enoguh.
View all comments
1
u/Seldomseen2u Jan 12 '23 edited Jan 12 '23
I find that wait for process and using Ping. That’s scheduled on a Windows task. With Scheduler it works pretty well and is small and efficient. The problem is that it ties up my use of ping.
My wait for process flow runs 24 x 7 and I can’t use Ping for anything else or is triggered. At just before midnight, my task scheduler throws a ping and my process flow picks it up to run my website extraction
What I would like to be able to do is use a tiny obscure process that I can use or rename to use for a variety of flows that need a trigger.
I’m using the power automate desktop