Microsoft list showing duplicate Request IDs

[laura_marsden]

Hi all,

HELP! Seeking help with an issue that has all of sudden popped up which I have no idea how it happened. 

My SharePoint list has items added to it via form, through Power Automate. The items were added in numerological order, but then all of a sudden they started duplicating out of nowhere??

So up until the 29 January it was adding items in order like (2835, 2836, then 2837) shown here: 

Then it started creating items with the same request ID starting from 2838, but different form submissions: 

Could anyone please help me work out why this might be happening? 

TIA 🙂

[SudeepGhatakNZ]

What is your Power Automate trigger?

[laura_marsden]

This is my flow trigger:

My compose is set up with: first(outputs('Get_items')?['body/value'])?['site']

I then have a condition to copy the attachments to a new file.

The I have connectors to send an emails:

I've gone through each part of my flow and I can't seem to work out what happened? 

[SudeepGhatakNZ]

@laura_marsden ,

I see that the items got created in the list on different dates. That confirms that they got created in two separate instances. Are you able to look at the flow history for both those instances? It is unlikely that they have the same response id.

You can also export the Forms data in excel and validate if the Response Ids match the Title

[laura_marsden]

The excel shows they are the same ID, but on different dates:

If I look at the flow, Request ID 2855 has a different ID number:

to this one with the same Request ID:

It is quite odd too that the creation time of these don't match what time it says on the list. The one just above shows it was created on 5/2/2024 at 4:43am, but it could not have been as that is outside our hours. It should on the list that it came through on the 6/2/2024. 

Is there a time lag causing these issues?

I think I understand that the ID number won't match the request ID number, but that doesn't explain why the Request ID is being used when it's already been used in another entry. 

[SudeepGhatakNZ]

@laura_marsden 

I think this is what might be causing it.

If users are allowed to update their response, the ID wouldn't change

You can now save and edit your survey responses - Microsoft Community Hub

[laura_marsden]

No they're not able to update their response through forms. We've got this specifically turned off there. But they could manually change it in the list, but this s unlikely. It seems more like the flow has glitched and gone back in numbers in the Request IDs to start again.  

They're completely different requests, using the form, by different people in different teams. But somehow they have been added to the WF list through the Flow as a Request ID number that has already been used. 

How could that happen? 

P.S. I realised that my note about the time of job and possible lag is not valid. It works in US time, and I'm in Australia. 

[wyattdave]

It's because you are using the request Id, use id instead as that is always unique.