Unanswered

How to maintain 50 bots of Power Automate Desktop simultaneously and single handedly, is there any process to do this ?

(0) Share

Report

Posted on by Bh12

How to maintain 50 bots of Power Automate Desktop simultaneously and single handedly, is there any process to do this ? thanks.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (2)

Answers (0)

MichaelAnnis 5,727 Moderator on at

Like (2)

Report
Excellent documentation

clear comments in your flows

my documentation is procedural (step-by-step). As I add automation, I modify the steps for the user, but leave the original and highlight them, indicating all these steps are being done by the bot.

Your documentation should list every input and output and other automation/processes those relate to. For example, if I am documenting process 2 which has an input of a filename from process 1, I want to list both of those in my process 1 documentation. So, I know that if something changes in 1, like the filename, I know I now have to change process 2 to accept the new filename.

An RPA framework. This is a set of rules by which you run all 50 bots. For example, filename formats are always the same: YYYY_MM_DD_Client_filename. Variables are always the same such as BDLM_mmddyyyy_slash means Begginning Day Last Month in MM/dd/yyyy format, and everybody knows it. Structure is the same. Ex. We don’t use Main flow except to call other flows and/or subflows.

Never repeat ANYTHING twice. Ex. Login to QBO. Maybe you use this same process across 8 flows. No need, make it once, and have the other flows call it. Don’t even use a folder name twice. Make it a variable, and use the variable. Why? Ex. Server upgrade made me add 02 to all my folder names. Folder names weren’t under a variable. Should have been an environment variable and I could have changed it one place.

Create a ticket system. A cheap solution would be Monday.Com. You can create forms for employees to fill out when a bot malfunctions. Submitting a form will create an item on your board, and you can manipulate the item from there (putting it through a process, updating its status, adding time spent on it, changing the priority, etc.

Have a proper upgrading policy. I hear a lot of people say “the last update killed my bot”. I have a full article on my LinkedIn regarding proper upgrade procedures. In summary, Upgrade on another system, test, then upgrade the original computer.

Feel free to message me if you need more ideas or professional help with implementing any of these ideas.

Was this reply helpful? Yes No
JS-27111534-0 6 on at

Like (0)

Report

Currently, there is no effective way to achieve this, unlike other RPA platforms where such features have been standard since 2015. It appears this software was not originally designed with large-scale enterprise environments or high bot volumes in mind. This limitation suggests that such use cases may not have been anticipated during its initial development.

Was this reply helpful? Yes No