![]() It also checks for 10 jobs tagged as 'uncategorised' and sends a link to the workqueue for someone to categorised them. Once complete they update the jobs category and status.Īny jobs that can't be processed due to not meeting standard responses are tagged in the workqueue as 'uncategorised'.Ī flow checks every hour if there are 100 jobs categorised, if they are it then packages them up and passess them to a Power Automate Desktop worker to process on an on prem system. One flow picks up all emails and saves them as jobs in a workqueue.ĭue to volume and complexity the work is then split to 2 service accounts, one doing even jobs, one doing odd. So here's an example of how a workqueue can be powerful. With a workqueue a process can be split, with one account with one set of access doing part, and an another with different access doing another part. ![]() An example would be 2 accounts, one picking up even jobs, the other odd.Īgain another fringe case, but in some scenarios security may not like one account having too much access to too many systems. By passing jobs into a queue different service accounts can pick them up and run the flow. Microsoft offers 2 solutions, an api add on, or a Flow only license (250,000 api calls), both not cheap. The 40,000 Power Platform api call limit can be hit. This is obviously a fringe case, but let's imagine you have a complex or a very high volume flow. Distribute to different flows to keep under API limits They then work directly in the workqueue, approving, rejecting or updating them in bulk.ĥ. But with a workqueue you can block approvals, so you could set a schedule to send current open approvals to the approver. Imagine having a hundred items that need approving, sending them one at a time would definitely become annoying. But having a workqueue you can set a flow to only run when there are 100 jobs in the queue.Īpprovals and Emails with options are a great human in the loop tool, but sometimes they can become almost spam. Scheduling runs normally covers waits, but what if you have a certain threshold instead, lets say when there has been a 100 responses in a form. ![]() ![]() Its not possible to set that in a trigger condition, but a workqueue allows you to create a job, and have conditions on that job to run only if all emails have been tagged as arrived in the job. So lets say you have a process that needs 3 emails with certain information before it can run. The example I use all the time is block runs. You may think that Power Automate trigger conditions cover everything, but they don't quite. Having a log of all successful and failed runs/actions, is great for debugging, load planning and generating Return on Investment reports. The main reason is that they also track successful runs (Power Automate run logs are terrible, max 100 or 30 days and no easy way to extract it). There are multiple ways of reporting exceptions, but workqueues to it best. So let's dive in and show why, and how easy it is to create a workqueue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |