Power Automate: Fix Duplicate Actions

Key insights

• Duplicate actions: Power Automate flows can send duplicate emails or create duplicate Planner tasks when the same action runs more than once.
  Check run history for repeated action entries to confirm the problem.
• Loops and stuck iterations cause most duplicates: an action placed inside an unwanted loop will run for every item.
  Fix it by moving the action outside the loop, using trigger outputs directly, or narrowing inputs before the loop.
• Get Items default limit — SharePoint returns 100 items by default with no warning.
  Enable pagination in the action settings to retrieve up to 5,000 items on a standard license (and higher limits on premium) so flows don’t miss records and create duplicates.
• Use focused actions and logic: start with a trigger, then Get Items, apply Filter Array or conditions, and finally Update Item or Delete Item to tag or remove duplicates.
  Prefer filtering by dynamic content instead of blind "Apply to each" loops to improve speed and avoid repeats.
• Trigger-specific fixes: flagged emails and some older templates often cause repeats for Planner or SharePoint flows.
  Rebuild or update those flows, add clear filters (for example, specify a Planner bucket) and avoid flaky trigger patterns.
• Community participation: use the Power Platform community to find tested fixes and examples.
  Answering questions and reviewing community solutions speeds learning and helps you adopt reliable patterns that prevent duplicates.

Introduction

Microsoft published a recent YouTube video in the Ask a Community Pro series that showcases expert tips for troubleshooting flows in Power Automate. In this episode, Scott Shearer demonstrates practical fixes for common issues such as duplicate emails and repeated Planner tasks, and he walks viewers through diagnostics and settings. Importantly, the video highlights a silent default in SharePoint that causes unexpected behavior unless corrected. Consequently, the presentation blends demos with clear steps so builders can reproduce the fixes in their own environments.

Moreover, the video emphasizes community-driven learning and practical demonstrations. Scott explains how answering questions helped him learn faster, and he shows real examples using a sample list and Planner tasks. Viewers will find timestamps for each demonstration, allowing them to jump to specific tips. Therefore, the piece functions both as a tutorial and a case study in troubleshooting.

Common Causes and How to Diagnose

The video first examines why flows create duplicate actions, often producing repeated emails or duplicate Planner tasks. Scott points out that duplicated results frequently come from triggers or from actions that run inside unintended loops, and he demonstrates how to identify when an action is stuck inside an Apply to Each loop. For example, using dynamic content from a trigger incorrectly can cause the flow to iterate over more data than expected, which then fires actions multiple times. As a result, careful inspection of trigger outputs and loop boundaries becomes essential to accurate diagnosis.

Additionally, Scott recommends simple debugging steps that save time, such as temporarily adding logging actions or isolating parts of a flow to confirm behavior. He shows how to reproduce the duplicate behavior on a small scale before applying fixes at production scale. These diagnostics help teams understand whether duplicates come from the source system, the trigger, or the flow logic itself. Thus, the initial troubleshooting phase reduces guesswork and prevents unnecessary changes.

Get Items Default Limit and Enabling Pagination

A central revelation in the video is the silent default limit of 100 items when using the Get Items action with SharePoint. Scott demonstrates that flows often return only the first 100 records without error or warning, which can mask missing results and inadvertently cause duplicates when later logic expects all items. To fix this, he shows how to enable pagination and increase the item limit to 5,000 on a standard license, while explaining that premium options can support even larger volumes. Consequently, enabling pagination becomes a practical immediate fix for many list-processing scenarios.

However, Scott also explains tradeoffs when increasing page limits: larger payloads can slow flows and trigger throttling, and retrieving more items raises memory and processing concerns. He walks through a demo where enabling pagination retrieves all 200 test items successfully, clarifying both the benefit and the cost. Therefore, teams should test with representative data volumes and monitor run duration. Ultimately, balancing retrieval needs with performance constraints matters for reliable automation.

Tradeoffs and Technical Approaches

The video balances different approaches and highlights that no single method fits every case. For instance, filtering items at the trigger or using a targeted query reduces the data the flow processes and lowers the risk of duplicates, but it requires careful query design to avoid missing legitimate items. Conversely, pulling more data and then using Filter Array logic inside the flow can be simpler to implement, yet it increases runtime and may encounter limits or throttling. Therefore, architects must weigh simplicity, performance, and accuracy when choosing a pattern.

Scott also discusses rebuilding flaky flows as a practical tradeoff, noting that recreating triggers or replacing outdated templates can resolve intermittent behavior more reliably than patching complex logic. He warns about relying on Outlook flag triggers, which can behave inconsistently, and suggests using safer trigger patterns where possible. In short, a pragmatic approach often combines targeted queries, modest pagination, and clear update/delete logic to maintain data integrity without overcomplicating the flow.

Community Learning and Practical Recommendations

Finally, the video frames community participation as a fast path to expertise; Scott attributes much of his knowledge to answering forum questions and iterating on community examples. He urges viewers to test fixes in small environments, add clear tagging (for example, setting a Duplicate status field), and to use conditional logic before destructive actions like delete. By sharing real-world examples, the episode encourages readers to adopt repeatable patterns and to contribute back with their own solutions.

To summarize actionable steps from the video: inspect triggers and loop boundaries first, enable pagination thoughtfully when Get Items misses records, and prefer targeted filters when possible to reduce processing. Additionally, document and test each change at scale and engage with the community to validate edge cases. Ultimately, Microsoft’s episode offers a concise playbook that balances practical fixes with an awareness of tradeoffs, and it equips builders to prevent duplicate actions while keeping flows efficient and maintainable.

Keywords

Power Automate duplicate actions, Fix duplicate actions Power Automate, SharePoint duplicate items Power Automate, Prevent duplicate flows Power Automate, Remove duplicate actions Power Automate, Power Automate handle duplicate triggers, Deduplicate SharePoint items Power Automate, Troubleshoot duplicate actions SharePoint Power Automate