Hehe think of us at mechanics. essentially you have to bring the car too us if you want help.
We need to see your flow; we need to see a flow run where something was duplicated. A re-try while possible, should not duplicate the data, unless an error happened post (write) but before it did the next loop.
In that case, you should turn off retries and find out exactly what item is failing and being retried.
If you want help, you have to bring the car
1) your flow with inputs in design mode
2) a flow run where we can see the inputs and outputs
We would potentially have to look through 6682 loops to find the one that "may" have been duplicated.
I would recommend this, and it will help you in the future
Inside your loop that I assume you have, let's pretend you only have a single action (add row to a table). Do this please. Now you can share everything first and hopefully we can help but this will help you.
1. Add a scope and rename it try
2. Add two parallel scopes renaming them catch and success do nothing
3. Add a Send Email where you will email yourself the details of the Row you were trying to add but failed
4. Change the Add a Row to a table to turn OFF retries (set it to none)
5. In the catch Scope, click ... and change the Run After Settings to Error/Skip and Timeout
6. in the Success Do Nothing click ... and youll see it already says Success so just leave it
Now return the flow that caused you to have duplicates. and I do mean, open that run up, and re-submit it
it will now follow this pattern and we can figure out which one or ones are failing
AND get an email
And you can validate how many records are in the table now.
P.S. make sure the table has no rows.
Make sure you do not have any set Variables etc inside an Apply to each.
Do this one time and we should be able to isolate the issue better.
