POWER AUTOMATE — PROJECT 5🟠 ADVANCED
Resilient Invoice Ingestion Pipeline — the Try/Catch/Finally Scope pattern with tuned retries and durable exception logging.
Resilient Invoice Ingestion Pipeline
Scope: Try
AI Builder: Extract invoice fields
Dataverse: Create Invoice record
HTTP: Notify ERP
retry: 4x, exponential backoff
Scope: Catch
runs after Try: failed, timed out, OR skipped
Compose: capture error details
Dataverse: Create ExceptionLog
Teams: Alert AP Lead
deep link to failed run
Scope: Finally
runs after Try: succeeded, failed, skipped, timed out (all)
Update Dataverse: ProcessingStatus

ExceptionLog (Dataverse)

INV-8821 — HTTP action503 Service Unavailable
INV-8819 — AI Builder✔ (no error)
🔔 Alert sent to AP Lead — "INV-8821 failed after 4 retries. Open failed run →"

Circuit-breaker safeguard

If the ERP endpoint fails >5 times in 1 hour (queryable from ExceptionLog), stop retrying and escalate immediately — protects a struggling downstream system instead of hammering it further.
What this shows: the Catch scope's "Configure run after" checks all three failure states (failed, timed out, skipped) — not just "failed" — and the Finally scope always updates status regardless of outcome. The exception is logged durably to Dataverse, independent of Power Automate's own run-history retention, with a working deep link for fast triage.