Episode Details

Here’s the catch Microsoft doesn’t highlight: Power Automate’s run history is time‑limited by default, tied to your plan and license—and once that retention window passes, your approval trail is gone as if it never existed. That’s fine for Microsoft’s storage bill, but terrible for audits, investigations, or basic accountability; designing without permanent logging is like deleting your CCTV before anyone checks the footage. In this episode, we break down why run history is only a temporary debugging aid, how to build durable approval logs outside that buffer, and how to redesign flows so you can restart from a specific stage, use dynamic approvers, and keep escalations and reminders under control instead of flooding inboxes.

WHY YOUR FLOW HISTORY VANISHES (AND WHY IT MATTERS)

Power Automate’s run history looks comforting—until you realise it’s a rolling window, not a permanent archive. Retention is defined by your tenant configuration and licensing, so older approvals simply age out: great for cloud housekeeping, disastrous when HR, Legal, or auditors ask for proof from last year and your logs are empty. In the episode, we walk through how to check your real retention window, why screenshots don’t count as evidence, and how to move from trusting ephemeral run logs to writing structured approval records (dates, decisions, actors) into durable stores like Dataverse, SharePoint, or SQL that you actually control.

DESIGNING APPROVAL FLOWS THAT DON’T COLLAPSE

Most approval flows implode because they’re built as thin demos: single‑stage, hard‑coded emails, no state tracking, no restart concept. That works until org structure changes, people leave, or departments demand different rules—then your flow becomes a brittle monster of nested conditions nobody wants to touch. We show how to design for reality instead: store roles instead of individual addresses, look up approvers dynamically from AD, SharePoint, or Dataverse, and keep a persistent “stage” field so you can restart at the correct step without resending the whole process. The result is a modular, restartable approval engine that survives staff changes, rule updates, and errors without forcing you to rebuild from scratch.

ESCALATIONS AND REMINDERS WITHOUT THE SPAM STORM

Bad flows solve stuck approvals with brute force: wave after wave of reminder emails until people start ignoring everything from “Flow Notifications.” We unpack how to replace spam cannons with sane escalation logic—time‑based reminders with clear limits, reassignment rules when someone is away, and escalation paths that go to the right roles instead of everyone in CC. You’ll learn how to use persistent state and logging so you always know where a request is, who’s blocking it, and how to nudge or re‑route it without drowning inboxes.

WHAT YOU’LL LEARN

• Why Power Automate run history is temporary debugging, not an audit trail you can rely on.
• How to design permanent approval logs in Dataverse, SharePoint, or SQL with structured fields.

  Listen Now