{"id":110900,"date":"2017-09-22T04:39:03","date_gmt":"2017-09-22T11:39:03","guid":{"rendered":""},"modified":"2025-06-11T08:11:51","modified_gmt":"2025-06-11T15:11:51","slug":"download-history-recurrence","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/download-history-recurrence\/","title":{"rendered":"Download flow run history, build advanced recurring schedules and more"},"content":{"rendered":"

In the past couple of weeks we have added several new features that enhance the power of Microsoft Flow.<\/p>\n

Download Flow Run History<\/h2>\n

Microsoft Flow has always had a highly detailed history view, where you can click on a single flow run and see exactly which steps have succeeded or failed. However, if you have a large number of flow runs, it can be difficult to find a specific failure. Now, you can Download a CSV of your flow run history and use Excel (or any other tool) to search across all of your flow runs, see exactly when they happened, and even the inputs and outputs of most steps.<\/p>\n

\"\"<\/p>\n

To download your flow history, simply select See all<\/strong>\u00a0under Run History and then select Download CSV<\/strong>. You may want to choose a filter before you download it – for example, by looking only at Failed runs. Please note that it can take a few minutes to retrieve the CSV as it can contain a large amount of data. Once it is ready, select Click to download<\/strong>. Now you have a file you can open in Excel!<\/p>\n

\"\"<\/p>\n

There are two important limitations to be aware of. First, this feature will only download the first 100 runs returned by your filter. Second, there is a limit on the size of content that is included in each cell of the CSV. For example, if you download 10 MB file, you don’t want that file’s contents in a single cell in a CSV. Instead, the CSV includes a hyperlink to the file, so it is just one click away.<\/p>\n

Build advanced schedules to trigger flows<\/h2>\n

You can now build more advanced recurring schedules with the Recurrence<\/strong> trigger. For example, you can now build a schedule that will run a flow at 9 AM only on weekdays, or, a flow at 10 AM and 3 PM every day.<\/p>\n

\"\"<\/p>\n

To use this feature, be sure to select a recurrence interval of either Weekly<\/strong> or Daily<\/strong>. By using a weekly recurrence, you can chose which days of the week the flow runs on, or, even what hours of the day it runs at. Read more about scheduling flows here.<\/a><\/p>\n

IntelliSense when building expressions<\/h2>\n

When you open the new expression editor you now get tooltips that help you to enter an expression. As you type, the available expressions will appear. Once you select an expression, the parameters that you need to pass will appear:<\/p>\n

\"\"<\/p>\n

As you enter each parameter, the next one will be shown. You can also see how, as you type an expression, the color of the text highlights so you can see the input types.<\/p>\n

Connect to endpoints with user-based Azure AD auth<\/h2>\n

There is a new connector – HTTP with Azure AD<\/a> – that enables you to get data from authenticated endpoints, with user-based Azure AD or Windows authentication. Previously, you could use Service Principal authentication for HTTP actions, but this did not support user-based auth. Now, you can create a connection that will enable any user to connect to an HTTP endpoint.<\/p>\n

\"\"<\/p>\n

To set up the connection, you will need to provide a base URL and an Azure AD resource URL. For example, if you want to connect to Microsoft Graph, use https:\/\/graph.microsoft.com<\/strong> for both of these inputs. Then, you can make any HTTP GET on the Graph API that you want. If you enter \/beta\/me<\/strong>, you can retrieve your user details. Like the normal HTTP action, if you want to use certain properties from the response then you’ll need to use a JSON Parse<\/strong> action.<\/p>\n

\"\"<\/p>\n

This connector also works with on-premises Windows Authenticated endpoints. To set that, up select Connect using on-premises data gateway<\/strong> and enter your Windows credentials.<\/p>\n

Three more new connectors<\/h2>\n

In the past two weeks we also have released three other new connectors:<\/p>\n