Answered

PAD stops running while in console

(0) Share

Report

Posted on by LA-08041614-0

Hi community! I've been struggling with something. I have a PAD flow in which my steps are: first setting some variables, and then running two subflows. In the first subflow I've got to first launch new Microsoft Edge, and go to a web page, and next steps are inside this page. My issue is: when I run it while editing, it goes quite well. But if I try it from the console, it almost doesn't do anything. Just opens Edge, nothing more. I have some "Wait for web page content" steps like in the second attached image, so I'm not sure if the speed is the issue.

I also tried to add this step #9 "Wait 20 seconds" before the subflows and see if it would change anything, but it didn't. If I run it from the console it will open the browser in a few seconds, way less then 20 seconds. What could be happening?

Note: I'm trying to run it like this because I somehow want to schedule trigger for this at a certain time (I don't have paid license).

Thank you very much for the help!

Categories:

Power Automate Desktop

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

eetuRobo 4,518 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

I think the issue might be that you have saved the flow but haven't published it.
That would be the reason why it doesn't do the same things as when run from console. When you run it from the console you run the latest version you have edited but when you run it from the console you run the last published version. So your last published version might not have anything else than just the open Edge browser and no steps after that.

Version control (which includes the publish functionality) is fairly new and its easy to forget to publish the flow when you might just press Ctrl + S to save and forget to publish it.

So in the editor press the publish button and after that try to run it from the console.

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 1,681 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @LA-08041614-0,

If that is not a publish issue as suggested by @eetuRobo, then this is expected behavior. Power Automate Desktop web and UI actions require an interactive desktop session. When a flow is run from the console, PAD may launch the browser but cannot reliably interact with web content, so steps appear to be skipped. This is not a timing issue. To fix it, avoid UI automation for scheduled runs or ensure the session remains fully interactive.

How to fix or work around the issue / suggestions, you may try these
Option 1: Redesign to avoid browser UI automation
If possible:

Download files using direct URLs
Use APIs or HTTP actions
Avoid Send keys and UI clicks

This is the most reliable way to support scheduled or console‑based runs.

Option 2: Make the web automation more robust
If browser automation is required:

Replace fixed waits with Wait for page load or Wait for element
Use web selectors instead of keyboard navigation
Add actions to bring the browser window to the foreground
Reduce reliance on Send keys

This improves reliability but does not fully remove the limitation.

Option 3: Ensure the session is interactive when running
When triggering from the console:

The user must be logged in
The desktop must remain unlocked
The screen must not be minimized or locked

PAD UI actions require visibility and focus.

Option 4: Separate the flow into parts

One flow handles data preparation or downloads
One attended flow handles browser interaction

This limits UI automation to scenarios where a user session is active.

Was this reply helpful? Yes No
LA-08041614-0 6 on at

Like (1)

Report
Copy link

Link copied!

Thanks for the answers! It was indeed the publish thing. I guess it is kinda new, didn't see this before.

Was this reply helpful? Yes No