Power Automate: Preventing Duplicate Trigger Execution

Introduction

Have you ever submitted a form once, but Power Automate processed it twice and created duplicate records or files?

It can be confusing when the flow looks perfectly fine, yet the same event is processed multiple times. The issue may not always be inside the flow—it could be related to webhooks, retry mechanisms, or integration settings.

In this article, we'll explore why this happens, how to troubleshoot it, and how to prevent duplicate processing, using Jotform as a practical example. The same approach can also be applied to other webhook-based integrations.

How Does a Webhook Integration Work?

Before troubleshooting duplicate executions, let's understand the basic flow.

When an event occurs in an external application, a webhook sends information about that event to Power Automate.

For example:

User submits Jotform → Jotform Webhook → Power Automate → Process Data → Create File/Record

Ideally, one event should result in one flow execution.

If the same submission reaches the flow twice, the process can create duplicate files or records.

1. Check for Duplicate Jotform Webhooks

One of the first things to check is the Jotform integration.

For example, imagine you have configured one Jotform to trigger a Power Automate flow.

You expect:

1 Jotform submission → 1 webhook → 1 flow run

But if the Jotform has multiple webhook configurations pointing to the same process:

1 Jotform submission → 2 webhooks → 2 flow runs

As a result, Power Automate may process the same submission twice.

How to Troubleshoot

Open the Jotform integration settings and check how many webhook configurations are active.

Duplicate webhooks

Old webhook configurations

Multiple integrations for the same form

Webhooks pointing to the same Power Automate process

Remove unnecessary or duplicate webhook configurations.

2. Check Power Automate Run History

If duplicate files or records are created, don't immediately change the flow.

First, open:

Power Automate → Flow → Run History

Check whether there are:

Two separate flow runs

The same Jotform submission data in both runs

Different trigger times for the same submission

If there are two flow runs with the same submission information, the issue may be occurring before or at the trigger level, rather than in the actions inside the flow.

3. Review Retry Policies

Power Automate supports retry mechanisms for handling temporary failures. For example, if an action communicating with an external service times out, Power Automate may retry the operation. Retries are useful, but for certain integrations they should be reviewed carefully because the external service may have already processed the request.

Check the Retry Policy of relevant actions and make sure it matches the requirements of your integration.

4. Check Connection References

Connection references are especially important when using Power Platform Solutions across environments such as:

TEST/UAT

Production

For example, a Jotform-to-Power Automate integration may use a specific connection or service account.

Always verify that the flow is using the correct connection reference and that unnecessary or duplicate connections are not being used.

Best Practices

When integrating Jotform or other external applications with Power Automate:

Keep only the required webhook configurations.

Remove old or duplicate integrations.

Check Flow Run History when duplicates occur.

Review retry policies for important operations.

Use unique submission IDs where possible.

Verify connection references when moving solutions between environments.

Identify the root cause before adding duplicate-prevention conditions.

Conclusion

Duplicate records or files in Power Automate are not always caused by the flow's actions. The problem can originate from the external integration, webhook configuration, retry behavior, or connection setup. For Jotform integrations, a simple troubleshooting process is:

Jotform → Check Webhooks → Power Automate Run History → Check Retries → Check Connections → Identify Root Cause

By checking the trigger source first, you can often resolve duplicate processing without unnecessarily changing the flow itself.