In part 4, we will now look to create the flow that will populate the nested folder called Live Updates. More information on the folder structure in part 1.
We will base this post mostly around part 3 as they are very similar in what they do but with a few subtle changes and enhancements.
Please familiarise yourself with part 3 as this post will only discuss the changes required in order to achieve an hourly live update summary.
On the My Flows page, select the Flow you have created from part 3 and choose Save as, now rename the flow to Live Incidents – Hourly Update (or similar).
The first modification we will make will be at the beginning to the Recurrence trigger.
This will run hourly and it can help by reminding you of the issues that are live and may be affecting your tenant.
If you work in a 24 hour environment, then this should work well for you. but what if your company is Monday to Friday business hours, say 8am to 5pm. Do we really need a summary of live service incidents on a Saturday or Sunday or at midnight?
I would suggest not, so right after the Recurrence trigger but before we initialise variable TenantID, ClientID & SecretID we have the option to stop the flow from running if out with the time constraints. I have written a separate blog on this called So you just want Flow running in business hours - 8am to 5pm so you may want to integrate these steps for this one.
