One Form submission triggering Flow twice

[Stubbs09X]

Hi everyone,

I have a Flow which is triggered by a Form.  The Form is embedded within a SharePoint page which is displayed as a tab in a team.

The Flow is a simple 'sign in', which populates a list with the name, email address, job title etc. of the person who completed it.

The issue I am experiencing is... whenever I submit the Form to trigger the Flow, the Flow runs twice (almost simultaneously) as if I had submitted the same Form twice (simultaneously or in quick succession).

You can see from the screenshot where the Flow has run twice, each time from a single Form submission.

Has anyone experienced a similar issue?

Thanks in advance for any support.

[FCGALLEG]

Hi Stubbs09X

Could you please share a screenshot of your flow’s configuration?It seems an issue in the configuration of the flow.

Regards,

Javier

[Stubbs09X]

Hi FCGALLEG,

Thanks for your reply, please see the screenshots.  The switch cases are all identical and the error presents itself regardless of the case followed.  There is a parallel action which is just a message to say 'sign-in successful'.  The Flow is then terminated successfully.

I've recently has to 're-authenticate' my connections because my account in my client's tenant was inadvertently deactivated - could that have something to do with it?  I'm trying to look at my Connections (under the Data menu) but it keeps timing out 🙄

1: Trigger

1 (trigger)

2: Case example

2 (case example)

3: Parallel branch and terminate

3 (parallel branch and terminate)

[FCGALLEG]

Stubbs09X

The flow is running twice, but it duplicate the process or are different process?

Thanks.

[Stubbs09X]

Hi,

The flow runs twice after one Form submission.  The flow runs are identical and (almost) simultaneous - so duplicate.

A bit more (probably not helpful) info:  I can tell when both runs are simultaneous because my variable is in their to update (and not add) a list item if someone completes the Form with the same details (job title, in the case of my form).  If the second of the identical Flow runs happens shortly after the first (and not at the same time), the variable kicks in and updates the item created a couple of seconds earlier.  But more often the duplicate Flow run is simultaneous, meaning the variable doesn't pick up the duplicate entries and I get two of the same items in my list.

[kuzek]

Hi @Stubbs09X , any luck with this issue? My team encountered similar problem where the flow triggered twice upon new response submitted in Microsoft Form. No duplicate result in Microsoft Form, just in Flow. Thanks!

[KingJ]

When the Form is submitted it processes in our Flow 2x.  However running a Test from the Flow results in only one submission.

Our flow takes the Form output and formats the responses into an email.  We receive 2 emails when submitted from the Form currently.  It should be (and previously was) only one email.

[stamperadam]

Same issue here. My flow was only running once per form submission and is now running twice per submission. I have changed nothing in the flow. Has anyone had any luck correcting this issues?

[pmedina]

The very same issue here. Dont even know what to review...everything looks just ok.

[pmedina]

Hi all,

Somehow the issue is not happening again after I did:

- Turn off the flow

- Create a copy of the form

- Edit the flow to use the new form

- Turn on the flow 

- Test the flow with the new form ID

After i repeated the steps to use the original form ID again the flow was working as expected (one run per form response)

[jimr1]

Thanks for this suggestion.

We have 2 versions of the form: Test & Production, so that we can handle future updates to the flow and/or form.

Temporarily swapping the IDs in our production environment with the test version and then back appears to have addressed.

[Anonymous]

I can concur that replacing the form with a new copy and updating the form ID in the flow to the new one fixes this problem.

The issue must be with a corrupt form.

[erikregiovvarml]

I also got this issue and i have been able to reproduce it. 

Steps to do it: 

1. Create a solution in testenviroment with a Flow trigger When a new response is submitted save and export flow to another enviroment. 

2. Import flow in enviroment as a managed solution. 

3. Test the flow (this time it run as it should only once)

4. Go back to the unmanaged solution in the testenviroment and make som changes. 

5. Export the solution again 

6. Import the flow again.

7. Run the flow (now it runs twice)

Solution

1. Change formsid in the imported flow to something else and save the flow.

2. Change back the formID to the original. 

3. Test the flow now it only run once. 

[365-Assist]

@erikregiovvarml your Solution is great. 

I even found that even the following works.

1 - Remove last character from Form ID

2 - Save Flow

3 - Replace last character to Form ID

4 - Save Flow

[jennyfer1]

I too have flow, on submission of form, it triggers mail 3 times 😞 please help

[Goodatit]

This worked for me. Thank you!

[chico]

just felt victim to this very exact scenario.

Form that has been up and not modified for over a year, 
Companion Flow to capture new submissions, also not modified for over a year.

They do not get Tremendous use, but we can say safely that about 1-2 submissions on average per week.

Early this AM it started running duplicates flows as if there was (2) submissions at nearly the exact same time.

Very easy to replicate the issue and watch the process runs twice.

Tons of good info here on possible solutions,
I created a back up before attempting any modifications and the idea of duplicating sounded very appealing, but I loathe having to involve other teams to change the re-direct URL to the existing Form....

Lucky for me, just turning off the Flow for a few minutes and coming back to enable and test was enought to flush the gremlin.

[AgainOpen]

I am having the same problem! I created the flow back in December 2022 and it's been working OK, with no problems until a few weeks ago, when it starting duplicating the outcomes. So when a New response is submitted generate 2 authorization requests, 2 entries on a SharePoint list and 2 emails - before that it was working perfectly as intended.

Not a clue what to do