Komatsu Australia accelerates hyper automation with Power Automate – from licensing to production in 4 weeks
Komatsu is an industry-leading manufacturer and supplier of equipment, technologies and services for the construction, forklift, mining, industrial and forestry markets. This article describes how a team at Komatsu Australia built a Robotic Process Automation (RPA)...
Power Automate for desktop – June 2022 update
Power Automate for desktop comes with new additions in June 2022 release, including the support of more data types for input and output variables and the ability to trigger desktop flows via an external link.
Workflow Start Threshold and Throttling
Topic
Nintex Workflow Cloud (NWC) tenants have Workflow Start threshold of 10,000/hour per tenant.
Additional Information
Why does this threshold exist?
To provide a high-performance environment for all customers, in a fair usage environment.
Ensure our service operates reliably and predictably for all customers.
Avoid performance degradation incidents.
The threshold level is well above the typical usage for most customers. 97% of our O365 & NWC customers have workflow starts below 5,000/hour.
What is considered a ‘Workflow Start’?
Any request to start a workflow through any of the following channels: Manual start, Form Submission, Start Event (i.e. item added to SharePoint list), Component workflows (i.e. started from NWC API, Start Workflow action, etc.), or a Scheduled start.
How can the threshold be avoided?
Optimize request operations:
Add more granular conditions for a request to start workflows
Fewer requests per hour
Stagger requests throughout the day
Reduce the frequency of requests
What happens when the threshold is reached?
External starts (API calls, component workflows, etc.) – No new workflows start; Returns a 429.
Start Events – Workflow start is queued and retried in next hour.
Form submissions – Workflow start is queued and retried in next hour.
Scheduled workflows – Postponed until the next hour.
Additionally, an in-app banner message in Automate page will be displayed stating the following:
Due to higher volumes within the past hour some workflows have not yet started and are queued to commence shortly. For more information, please visit the manage workflow starts help document.
Playwright Assertions with Custom Matchers extended from Jest in Playwright Tests
https://www.youtube.com/watch?v=QYYsYFSbUkI
Using the Power Platform to Automate the Classification and Validation of US Vaccination Record Cards – Part 2
This is the second post in the series on how you can use the Power Platform to Automate the Classification and Validation if US Vaccination Record Cards. This is an extension of the Return to the Workplace Solution (RTW), which provides helpful tools for executive...
Soft Assertions in Playwright with Typescript
https://www.youtube.com/watch?v=kAld_glrfsc
New site template updates: new templates and the template history panel
It’s been exciting to see how all of you are using SharePoint site templates since we released the feature last year. These templates are intended to make it easier to get started creating a SharePoint site quickly and demonstrate the art of what’s possible with our...
Change owner of a solution flow
You can now change the owner of a solution flow from Power Automate portal. This feature enables owners, co-owners, and admins to change the owner of a solution flow to enable business continuity when the original owner switches teams or leaves the organization
Part 10 – Start every test with known set of data in Database with EF Core and Specflow
https://www.youtube.com/watch?v=_hT_aXoi12U