You’re offline. This is a read only version of the page.
69
I found a problem with Power Automate Desktop (PAD) generating errors in my flows that call other flows. About a year ago, I could use copy and paste to create back-ups of my flows. I press ctrl A to highlight the entire flow in the PAD editor, press ctrl C to copy, switch to Notepad and press ctrl V to paste the text, and then save it. On the runflow statements, the pasted text showed the input and output variables. At some unknown time, the copy function (ctrl C) stopped including the input/output variables in the copied text. As I edited the flows and re-installed from the back-up text files, I saw editor errors complaining of missing variables or running the flows causing strange runtime errors, mostly null references.
Of course, the people here think that I am to blame, when it is the copy function (ctrl C) of the PAD editor that is causing the errors. Combine that problem with my PAD flows randomly disappearing due to an implementation error in the name hashing on the server side, I am about to abandon PAD.
Quality Assurance (QA) is severely lacking.
Share
Report
All responses (
Answers (
