Duplicate REQ with no information are created for every REQ

jlaps
Kilo Sage

We recently had a large project complete from a third party for our portal, and we just noticed this odd behavior where a second REQ is being created for every request, but this second REQ does not have any RITM associated and gets CLOSED INCOMPLETE. We are not sure where to begin to check for where this is coming from since the one REAL one seems fine. Ideas on what to check?

 

jlaps_0-1714488801458.png

 

6 REPLIES 6

Tim Deniston
Mega Sage
Mega Sage

Is there workflow or flow associated to the "empty" REQ? 

There is, but its exactly the same as the one that "works"-

jlaps_0-1714491698498.png

Blank REQ-

jlaps_1-1714491735042.png

Working REQ-

jlaps_2-1714491763932.png

Two REQs are being triggered, but only one has the info and is being processed (correct) and we need to prevent the second one from creating at all... somehow.

Are these being submitted by a user in the portal or a user in the classic view or a user in Workspace? Is there automation creating them (REST API) or inbound email action? 

 

Depending on the answer, these articles might help: 

These are being submitted through the Employee Center portal only. Checking your linked articles- thank you!