Powerful Platform reminder SOURCE STARTER v1.0.0, 2026-10-23
This is a manual flow blueprint, not an importable Power Automate package.
Do not upload the ZIP to Import solution. Build manually in a test environment.

Dependencies and costs: authorized Power Automate account, SharePoint list access,
notification connector and applicable licenses. Confirm current tenant entitlements
and connector classification. Premium additions require separate assessment.
No promise of zero platform cost. No private data, endpoints or connection IDs supplied.

Requests schema: Title text; Status choice Open/Completed/Cancelled; DueUtc date/time;
Owner person; LastReminderUtc optional date/time.
DeliveryLog schema: Title unique text (delivery key); RequestId number;
State choice Pending/Sent/Unknown/Failed/Skipped; AttemptUtc date/time; ErrorSummary text.
Restrict log access. Do not store whole private payloads.

Manual flow blueprint:
1 Recurrence daily at business timezone/hour. Use one worker; verify no overlapping runs.
2 Capture run timestamp. Retrieve open overdue candidates with tested filters and pagination.
3 Re-read request. Skip closed. Missing/invalid date or owner -> review. Future due -> skip.
  If LastReminderUtc is less than 24 elapsed hours ago, skip. Future last-sent -> review.
4 Claim a unique delivery key: request + due-date version + stage + business date.
  Existing key -> inspect its state, do not automatically resend.
5 Recheck status. If closed, mark Skipped. Otherwise send only to test recipient in pilot.
6 On confirmed connector acceptance mark Sent and update LastReminderUtc.
7 On timeout or uncertain outcome, route to operator review; do not blindly repeat send.
  Log update failure after successful send is also uncertain for subsequent runs.
8 Catch failures/timeouts through Run after scopes. Independently monitor missing runs.

Limitations: not exactly-once delivery. Status can change after recheck. Cooldown is
24 elapsed hours, not one per local day; date-bucket keys are a separate safeguard.
Define reassignment, changed deadlines, weekends and supervisor fallback explicitly.

Tenant test checklist: missing dates and owners; completed/cancelled; exact due boundary;
DST; more than one query page; concurrent runs; close-before-send; date changes;
denied access; timeout after send; log failure; rerun. Use approved test recipients only.

Validation: local JSON parsing, required file checks and ZIP CRC only. No tenant import,
Power Automate expression execution, connector calls, notifications or concurrency tests.
