flow.microsoft.com Open in urlscan Pro
40.68.225.143  Public Scan

Form analysis
0 forms found in the DOM

Text Content

We use optional cookies to improve your experience on our websites, such as
through social media connections, and to display personalized advertising based
on your online activity. If you reject optional cookies, only cookies necessary
to provide you the services will be used. You may change your selection by
clicking “Manage Cookies” at the bottom of the page. Privacy Statement
Third-Party Cookies

Accept Reject Manage cookies
"Skip to main content"
Power Automate
 * Product
   * Connectors
   * Templates
 * Capabilities
   * Digital process automation
   * Robotic process automation
   * Business process automation
   * Process advisor
   * AI Builder
 * Pricing
 * Partners
 * Learn
   * Blog
   * Documentation
   * Roadmap
   * Self-paced learning
   * Webinar
   * Business process and workflow automation topics
 * Support
   * Overview
   * Issues
   * Give feedback
   
 * Community
   * Overview
   * Forums
   * Galleries
   * Submit ideas
   * User groups
 * Sign in
 * Sign up free
   
 * More

 * Sign in
 * Sign up free
 * 


 1. Product updates


ERROR HANDLING STEPS, COUNTERS, A NEW FLOW DETAILS EXPERIENCE AND MORE

Stephen Siciliano, Vice President, Power Automate, Wednesday, May 24, 2017




ERROR HANDLING

From time-to-time, things don't work out exactly as you expected in your flow —
that's where error handling comes in. With error handling, you can define any
number of steps to run after the failure of an action. This powerful new feature
will ensure that you can run even your most important business processes inside
of Microsoft Flow.


HOW TO ADD AN ACTION AFTER A FAILURE

First, you'll have to figure out which action you want to monitor for failures.
If you already have actions after that step, you can add a new step after in
parallel. In this example, let's look at adding an error handling step for the
Dynamics 365 action Create a new record:



You can then select what action you want. Once you have a new step, select the
"…" menu at the top-right of the action and choose the Configure run after menu
item:



This will display the new options. You can define steps that run after:

 * An action has any type of failure (except timeout).
 * An action was skipped. Actions are skipped either when a condition is not
   met, or, when a previous action before that action fails.
 * An action times out. This can happen if the call to the backend times out
   (120 seconds), or for long running actions such as approvals, after 30 days.



Select any or all of these checkboxes and then select Done. Now, you will get a
mobile notification whenever the flow fails to create a new record in Dynamics
365.


USE RUN AFTER TO HANDLE MISSING RECORDS

There are even some cases where error handling may even be part of the
"expected" flow. For example, if you are copying records into a system and you
want to have different behavior depending on if the record exists. Or, you want
to look up someone in the directory, and then if the user doesn't exist you want
to use some default values. You can set this up by having an action run after
the Office 365 Get user step fails and populate the default data:



The above template shows how this works. It reads a record from Dynamics 365 and
tries to look up that user's email in the Office 365 directory. If the user is
found, then a task is created in planner with that email address. Otherwise, the
task can still be created in planner, but it won't have email information. 


INCREMENT OR DECREMENT COUNTERS

You can initialize and increment or decrement variables inside of a flow run.
This will make it possible to know how many times a certain branch of logic ran,
for example.

To get started you'll first need to initialize the variable:



Currently, you can create counters that are Integers or Floats (numbers with
decimals). Once you have initialized the variable you can then increment or
decrement it in your flow. Finally, you can also then reference that variable
wherever you want.



In the above flow you can see at the top the variable is initialized, it's
incremented inside a condition in a apply-to-each loop, and then at the end a
notification is sent with the contents of the variable.


VIEW ORGANIZATION QUOTAS

Inside of organizations, the number of flow runs you have is a quota that's
shared across all users in the company (see the Microsoft Flow Pricing page).
Now, tenant administrators can see how many flow runs have been used by members
of their org in the Microsoft Flow Admin Center. 



Note that trial (or free) users do not count against the organization quota, but
they are included for visibility if the admin wants to understand trial usage.
Second, we have added a details view to help admins understand the distribution
of licenses inside their org and how each of these licenses are contributing to
the quota:



The Quota Breakdown view lists the number of runs per license, the number that
are purchased, and thus what your total run capacity is. Finally, you can always
purchase additional Flow Runs if your company is nearing its quota at the end of
the month.


FLOW PROPERTIES PAGE

Starting this week, when you go to your My flows list and select a flow you'll
see a new flow details page (instead of the flow designer itself):



This new page gives you a quick glance at everything that is immediately
relevant for your flow, including:

 * The connections that this flow uses, and their status (to easily see if a
   connection is broken)
 * Who has access to the flow
 * The run history of the flow including both successful and failed runs 

To edit a flow you, the the pencil icon on the My flows list, or, select Edit
flow in the toolbar on the properties page. You can still access the flow runs
page to get the full list of every time that the flow has checked its trigger or
failed by selecting the See all link on the Run history tile.


USE DIFFERENT HTTP METHODS AND ADD PATH SEGMENTS FOR THE REQUEST TRIGGER

The Request trigger is an easy way to have your application invoke a flow
directly. The Request trigger now has the ability to define a different method,
so you can use an HTTP GET or a PUT for example. In addition, you can define
additional path segments that get added to the URL and then use the values the
user passed in those segments in your flow.




TWO NEW SERVICES

Finally, we have two new partner services available this week:

 * Parserr – Automate your business and eliminate unnecessary manual data entry.
 * Cognito Forms – Cognito Forms lets you easily build powerful online forms,
   such as surveys, order forms, registration forms and more. For free.



WHAT IS POWER AUTOMATE?

Power Automate is a service for automating workflow across the growing number of
apps and SaaS services that business users rely on.

Read more

SUBSCRIBE TO THE BLOG

Subscribe

SEARCH BY CATEGORY

 * Developers
 * Flow of the Week
 * Microsoft Power Automate
 * Product updates
 * Stories
 * Walkthroughs
 * Webinars

ARTICLES BY DATE

 * January 2023
 * December 2022
 * November 2022
 * October 2022
 * September 2022
 * August 2022
 * July 2022
 * June 2022
 * May 2022
 * April 2022
 * March 2022
 * February 2022
 * January 2022
 * December 2021
 * November 2021
 * October 2021
 * September 2021
 * August 2021
 * July 2021
 * June 2021
 * May 2021
 * April 2021
 * March 2021
 * February 2021
 * January 2021
 * December 2020
 * November 2020
 * October 2020
 * September 2020
 * August 2020
 * July 2020
 * June 2020
 * May 2020
 * April 2020
 * March 2020
 * February 2020
 * January 2020
 * December 2019
 * November 2019
 * October 2019
 * September 2019
 * August 2019
 * July 2019
 * June 2019
 * May 2019
 * April 2019
 * March 2019
 * February 2019
 * January 2019
 * December 2018
 * November 2018
 * October 2018
 * September 2018
 * August 2018
 * July 2018
 * June 2018
 * May 2018
 * April 2018
 * March 2018
 * February 2018
 * January 2018
 * December 2017
 * November 2017
 * October 2017
 * September 2017
 * August 2017
 * July 2017
 * June 2017
 * May 2017
 * April 2017
 * March 2017
 * February 2017
 * January 2017
 * December 2016
 * November 2016
 * October 2016
 * September 2016
 * August 2016
 * July 2016
 * June 2016
 * May 2016
 * April 2016




POWER PLATFORM

 * Overview
 * Power BI
 * Power Apps
 * Power Pages
 * Power Automate
 * Power Virtual Agents

--------------------------------------------------------------------------------

 * Sign up free
 * Sign in


BROWSE

 * Templates
 * Connectors
 * Partners


DOWNLOADS

 * Mobile
 * Gateway


LEARN

 * Documentation
 * Learn
 * Support
 * Community
 * Give feedback
 * Blog
 * Pricing

--------------------------------------------------------------------------------

 * 
 * © 2023 Microsoft

 * 
 * 
 * 

 * Contact us
 * Trademarks
 * Privacy & cookies
 * Manage cookies
 * Terms of use
 * Terms & conditions
 * English (US)
   * العربية
   * български
   * català
   * čeština
   * dansk
   * Deutsch (Österreich)
   * Deutsch (Schweiz)
   * Deutsch (Deutschland)
   * Ελληνικά
   * English (Australia)
   * English (Canada)
   * English (Cyprus)
   * English (UK)
   * English (Ireland)
   * English (India)
   * English (Malaysia)
   * English (New Zealand)
   * English (Singapore)
   * English (US)
   * English (South Africa)
   * español (España)
   * español (México)
   * eesti (Eesti)
   * euskara (euskara)
   * suomi
   * français (Belgique)
   * français (Canada)
   * français (Suisse)
   * français (France)
   * galego
   * עברית
   * हिन्दी
   * hrvatski
   * magyar
   * Indonesia
   * italiano (Svizzera)
   * italiano (Italia)
   * 日本語
   * 한국어
   * қазақ тілі
   * lietuvių
   * latviešu
   * Melayu
   * norsk bokmål
   * Nederlands (België)
   * Nederlands (Nederland)
   * polski
   * português (Brasil)
   * português (Portugal)
   * română
   * русский
   * slovenčina
   * slovenščina
   * српски (Србија)
   * srpski (Srbija)
   * svenska
   * ไทย
   * Türkçe
   * українська
   * Tiếng Việt
   * 中文(简体)
   * 中文(繁體)

California Consumer Privacy Act (CCPA) Opt-Out Icon Your California Privacy
Choices