Answered

Power automate flow

(2) Share

Report

Posted on by IB-22040114-0

Hi everyone,

I’m currently building an SLA-based email tracking and reminder system in Microsoft Power Automate, and my solution is split into 3 flows:

Flow 1: Email intake → store data into SharePoint list
Flow 2: Calculate SLA timestamps

StartSLADateTime
WarningDue (+4 hours)
BreachDue (4 hours after WarningDue)

Then update SharePoint

Flow 3: Business hour validation, reminders, and escalation emails (currently still designing this part)

I’m currently focusing on designing Flow 3.

Based on this structure, I would really appreciate any feedback or best practices on whether this separation is suitable or if there’s a better approach for SLA handling (especially around business hours and email reminders).

I’m still a beginner, so any suggestions are very appreciated. Thank you!

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Verified answer

Vish WR 3,748 on at

Like
a
(3)

Report
Copy link

Link copied!
@IB-22040114-0

Splitting the solution into separate flows for intake, SLA calculation, and reminder/escalation logic is a good modular approach and makes troubleshooting much easier later. Best practice guidance for Power Automate generally recommends smaller reusable flows instead of one large, complex flow

Store all SLA timestamps directly in SharePoint (which you already do) so Flow 3 only checks status and timing.

For business hours, avoid hardcoded calculations if possible. Use a central configuration list for working hours/holidays.

Use a scheduled flow for reminders/escalations instead of long-running delay actions — it’s more stable and easier to maintain.

Be careful with time zones since SharePoint stores dates in UTC and this commonly causes incorrect SLA reminders/escalations.

Add Status column

New

Warning Sent

Breached

Closed

That will make the reminder logic much cleaner.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
Your 3-flow architecture is actually aligned with good enterprise design principles.

The best improvement now is:

Make Flow 3 a centralized SLA monitoring engine

Use recurrence-based monitoring instead of Delay Until

Externalize business hours/holiday calendars

Add duplicate-notification protection

Keep SLA calculation isolated from intake processing

Consider Dataverse if volume/scalability increases

Your current separation is already much better than the common “single giant SLA flow” anti-pattern many teams build initially.

Was this reply helpful? Yes No
IB-22040114-0 43 on at

Like
a
(2)

Report
Copy link

Link copied!

Thanks for the info and suggestions! It really helps me to refresh my thinking and gave me a clearer direction for improving my current flow. I really appreciate it!

Was this reply helpful? Yes No
Vish WR 3,748 on at

Like
a
(2)

Report
Copy link

Link copied!

@IB-22040114-0

Anytime. Not just helped you helped us too on refreshing things

Enjoy the flow design 😀

Was this reply helpful? Yes No
IB-22040114-0 43 on at

Like
a
(0)

Report
Copy link

Link copied!

Recurrence
│
├─ Get Items
│
│
└─ Apply to each (filtered items)

├─ Filter Array
│ WarningDue <= utcNow()
│ AND FlowStatus = 'Active'
├─ Send Email
└─ Update Status = 'Warning Sent'

I already done the for the flow 3, but here is the problem.
1. The flow run successful but the email firing even not fall into the DueDate.

2. After looking at the history for checking but the flow show after the loop is skipped. When the email run successful the item can see the input and the output.

Was this reply helpful? Yes No