PAD SLOW!!!! Not ready yet to leave WinAutomation

(1) Share

Report

Posted on by Hvus

Dear developers from PAD,

As far I used the PDA it is not ready yet to be in use and migrate from WinAutomate all the scripts.

The principal issue is SLOW.

Then the structure in order to organize the scripts.

We need more time than January to stop using WinAutomation. Because the PDA is not ready to go to production.

Thank you

Categories:

Power Automate Desktop

I have the same question (0)

All responses (11)

Answers (0)

Sort by

Highboy 1,187 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Slow how?
We are using it in our production environment, and although it still needs a "little" tweeking from Microsoft, it works great (let's forget all about 2.14)
In our environment it's very stable.

Was this reply helpful? Yes No
Kresimir_RPA 286 on at

Like
a
(0)

Report
Copy link

Link copied!

In my case, working in PAD is frustratingly slow. Just dragging any action to working field or right clicking enabling/disabling an action takes about 3 seconds to complete. Basically every click in PAD takes 3 to 4 seconds. It's very frustrating. Do you guys having the same issue? I was convinced that it's because of cloud environment.
In Softomotive ProcessRobot everything worked fast and instantly.

Was this reply helpful? Yes No
Highboy 1,187 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

We came from ProcessRobot, and I agree that it was faster, and in many ways better.
But three seconds, is very long time, and my colleage and me does not have that kind of problem.

Was this reply helpful? Yes No
Kresimir_RPA 286 on at

Like
a
(0)

Report
Copy link

Link copied!

Do you have big and complex flows? I've noticed that it is much slower when you have process with many subflows that have many lines of code (over 100 lines).

Was this reply helpful? Yes No
Highboy 1,187 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Very big and somewhat complex flows all the way 😊

Was this reply helpful? Yes No
geavgous Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Kresimir_RPA and @Hvus ,

Thanks for trying out Power Automate. Could you please share your PC specs and let me know, what else is running in the background, in an aggregated manner (e.g.. Total CPU utilization etc.).

Thanks,
George

Was this reply helpful? Yes No
Kresimir_RPA 286 on at

Like
a
(0)

Report
Copy link

Link copied!

Windows 10 64bit
Intel i58350U 1.9GHz
16GB RAM

Usually I have Chrome and Edge running in background with 10tabs each, Skype, Outlook. But even when I close everything but PAD, it still works slow.

Was this reply helpful? Yes No
Hvus 33 on at

Like
a
(1)

Report
Copy link

Link copied!

Not at all. The PAD run nice the scripts. That's not the problem.

The problem is the editor, the manipulation of the script. Where you spent a lot of time in developing or constructing as a programmer it is a nightmare to build nothing. Desesperate.

The resources are not the problem, they are plenty and nice (cpu, ram and space).

Was this reply helpful? Yes No
Hvus 33 on at

Like
a
(0)

Report
Copy link

Link copied!

Sure, thank you for asking.
Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz 2.40 GHz (2 processors), 16 GB Ram, 100 gb , Windows 10 Ent.
12% CPU, 31% Memory,0% HDD.

Was this reply helpful? Yes No
Kresimir_RPA 286 on at

Like
a
(1)

Report
Copy link

Link copied!

That's right. Working in editor is the problem, every click, drag &drop, changing subflow tabs, moving actions up and down and even just scrolling up and down when you have 300 or more lines of code takes time. I'm working three times faster in ProcessRobot so I'm currently developing in ProcessRobot and when I'm close to finish and testing I'll go and migrate the process to PAD. And one other thing..Regions would help in cases where you have 500 or more lines of code so you could collapse it and brake flow into sections. It would make the flow easier to read and manipulate it, but that's another issue.

Also when flow fails and you want to see and debug on which action it failed in 'Monitor->Desktop flow runs' it is hard to see and find it when you have 1000 or more lines of code. It would be helpful if the actions would be arranged and numbered.

Regards,
Kresimir

Was this reply helpful? Yes No