Comece agoraComece grátis

Início
Cursos
Intermediate Power Automate

Run-after: catching failures gracefully

Create Your Free Account

or

Email Address

Password

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.

Este exercicio faz parte do curso

Intermediate Power Automate

IntermediárioNível de habilidade

5.0+

Comece o curso gratuitamente

Detect upcoming contract renewals before they lapse. Walk through the three Power Automate trigger families, pick the right one for a real-world automation problem, configure time zones so a scheduled flow fires when users expect, and add trigger conditions that stop the flow from running on weekends.

Exercise 1: Picking the right trigger Exercise 2: Match the scenario to its trigger type Exercise 3: Why doesn't a Recurrence trigger fit here?Exercise 4: Scheduled triggers Exercise 5: Build the daily renewal sweep Exercise 6: Spot the wrong time-zone setting Exercise 7: Why are there no weekend runs?Exercise 8: Automated triggers and conditions Exercise 9: Build a "renewal submitted" automated flow Exercise 10: Add a weekday-only trigger condition

Fetch, filter, and enrich contract records using SharePoint Get items with OData queries, resolve responsible partners via Office 365 Users lookups, attach contract documents with the correct link-vs-attach security posture, draft notification emails with dynamic content, and write back an audit trail so the flow remembers what it has already done.

Exercise 1: Getting data: fetching structured records Exercise 2: Add Get items for upcoming renewals Exercise 3: Where does this filter belong?Exercise 4: Why did Get items return 0 records?Exercise 5: Resolving people: the lookup pattern Exercise 6: Resolve the responsible partner's email Exercise 7: Which token gives the email address?Exercise 8: People-reference anatomy Exercise 9: Working with SharePoint documents Exercise 10: Look up the contract PDF and capture its link Exercise 11: Why does the recipient see "Access denied"?Exercise 12: Attach or link?Exercise 13: Notification and audit-trail write-back Exercise 14: Send notification and update the audit trail Exercise 15: What changed in the audit workbook?Exercise 16: Audit trail simulator

Route contracts by value with Condition actions and by status with Switch, guarding against type-coercion gotchas and silent Default misses. Then add run-after failure branches so one broken connector call doesn't kill the entire sweep, and close the diagnostic loop with test, run history, and Show raw outputs.

Exercise 1: Condition: branching on contract value Exercise 2: Branch the flow on contract value Exercise 3: Why does the Condition always take "If no"?Exercise 4: AND vs OR Exercise 5: Switch: routing by status Exercise 6: Replace nested Conditions with a Switch Exercise 7: Spot the missing Default Exercise 8: Switch builder sandbox Exercise 9: Run-after: catching failures gracefully

Exercicio Atual

Exercise 10: Add a "log failure to SharePoint" branch Exercise 11: Run-after state picker Exercise 12: Why didn't the failure-handler fire?Exercise 13: Test, run history, and the diagnostic loop Exercise 14: Find and fix the seeded bug Exercise 15: Which Flow Checker warnings matter?

Route high-value renewals through the Approvals connector, swap binary Approve/Reject for Custom Responses, and branch on the Outcome (capital-A casing trap included). Prepare the flow for production with shared ownership, run-only access, and connection continuity, then assemble everything into a capstone pipeline.

Exercise 1: Approvals fundamentals: Start and wait Exercise 2: Add an approval for high-value renewals Exercise 3: What does the approver see?Exercise 4: Why didn't the "If approved" branch run?Exercise 5: Approval types and custom responses Exercise 6: Replace Approve/Reject with custom responses Exercise 7: Approval-type sandbox Exercise 8: Match the scenario to the approval type Exercise 9: Sharing, ownership, and going to production Exercise 10: Inspect the Share dialog Exercise 11: Owner or run-only?Exercise 12: Why does this flow keep failing after handover?Exercise 13: The full renewal pipeline Exercise 14: Assemble the final renewal pipeline Exercise 15: Renewal pipeline report card Exercise 16: Congratulations!