Answered

New "Run Flow" Connectors Dialog Box Breaks Scheduled Automations

(1) Share

Report

Posted on by KeithIMyers

Good Morning

It appears that a change was introduced in PAD 2.42.317.24061 that breaks one of my workflows. I have this workflow invoked by an application on my desktop to run after a few other applications are ran. It seems to work after clicking "Ok" on the dialog box but this breaks the ability for this task to run unattended on my workstation.

Screenshot 2024-03-18 101225.png

Steps to replicate

1) Create a Flow that connects into SharePoint and Office365 Outlook

2) Use the "Create Desktop Shortcut" to place a shortcut on your desktop

3) Launch the shortcut

Categories:

Power Automate Desktop

I have the same question (0)

All responses (15)

Answers (1)

Deenuji_Loganathan_ 6,250 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @KeithIMyers

Could you please disable the confirmation dialog and see whether it fixes your reported issue.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀. If you'd like to appreciate me, please write a LinkedIn recommendation 🙏

Was this reply helpful? Yes No
KeithIMyers 15 on at

Like (0)

Report
Copy link

Link copied!

@Deenuji - That box was already disabled, I wish it were that easy

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @KeithIMyers,
I can be able to reproduce your issue in my system. It appears that the recent updates, version 2.42 and 2.41(As few weeks back also some one from community reported the same issue) , exclusively display that popup. The only solution available is to revert to version 2.39 of Power Automate Desktop, where no such popup appears.

If you don't have access to Power Automate Desktop version 2.39, you can download it from here.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀. If you'd like to appreciate me, please write a LinkedIn recommendation 🙏

Was this reply helpful? Yes No
Verified answer

KeithIMyers 15 on at

Like (2)

Report
Copy link

Link copied!

Thanks, I was able to hack together a workaround via a new flow that does the following:

1) Uses the "run application" action
- Application : C:\Program Files (x86)\Power Automate Desktop\PAD.Console.Host.exe
- Args "ms-powerautomate:/console/flow/run?environmentid=Default-XXXXXXa4-033e-4a86-8f33-f0daeb12319f&workflowid=a075c324-3dbf-4ab7-XXXXX-513cffXXXXX4&source=Shortcut
2) Waits 30 seconds (likely excessive but it gives PA time to "download" the flow and launch it
3) Locates the "Run flow" window and sends the "Return" key

I then call this new launcher flow instead of the existing flow.

I am trying to avoid reverting back, that can sometimes cause problems. I just hope that this change is reverted back as it is more of a disservice.

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Moderator on at

Like (0)

Report
Copy link

Link copied!

@KeithIMyers

By the way, Excellent workaround for time being 🙂 Happy Automation.

Was this reply helpful? Yes No
KeithIMyers 15 on at

Like (1)

Report
Copy link

Link copied!

It's sort of poetic to use PowerAutomate to fix a problem introduced by PowerAutomate.

Was this reply helpful? Yes No
99999999sa 5 on at

Like (0)

Report
Copy link

Link copied!

Can you please provide a link to download version 2.39?

Was this reply helpful? Yes No
dysruptor 2 on at

Like (0)

Report
Copy link

Link copied!

@KeithIMyers I have been running into this as well, but in further testing, I think it's a limitation (probably a new "feature") that is inherently tied to using the Task Scheduler to invoke a flow. If you use a scheduled Cloud Flow instead that just calls the Desktop Flow, that seems to work fine and avoids that extra "run flow" prompt.

Was this reply helpful? Yes No
AuotmateCat 2 on at

Like (0)

Report
Copy link

Link copied!

Hello,
I'm new to Power Automate and I'm currently experiencing difficulties with the Dialog Box Breaks.
I'm unsure about how to proceed with Step 3:
3) Locates the "Run flow" window and sends the "Return" key
The recorder is unable to record the Power Automate Dialog box.

Was this reply helpful? Yes No
padpad 2 on at

Like (0)

Report
Copy link

Link copied!

The issue has not been resolved because flows cannot be executed in parallel.
What do those who have solved it do?

> 3) Locates the "Run flow" window and sends the "Return" key
I choiced key send flow.
Window title = "Run flow" ( manual input )

Was this reply helpful? Yes No