Duplicate REQ with no information are created for every REQ

[jlaps]

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?

[Tim Deniston]

I wonder if maybe the RITM has a business rule or the RITM workflow has an activity that is updating the REQ too quickly and thereby creating a duplicate record. 

[jlaps]

Hmm, there HAS been some recent activity to update fields on the RITM/REQ during insert, so this seems plausible. Not sure how to test for it, but it gives us something to look into. Thank you!