You will see this in a few places that will be addressed shortly (it won't fully eliminate the possibility but should drastically reduce the occurrence). One is during NewItem cancellation and the other is during StoreAlert Status resolver. When you need to cancel a duplicate service request, follow the SQL steps below. For NewItems, you may need to look up the ServiceRequest using info from the message. Refer to the NewItem ServiceRequest lookup help page and find the most recent SubBanner and ProductSku NewItemTracking record.


 

--Peek message of DL using ServiceBusExplorer and grab the ServiceRequestId from the message

SELECT * FROM [coordinator].[LinkedRequestSource] WHERE ServiceRequestId = '702e388e-6dee-4934-9f70-8075cb45fe67' --ServiceRequestId

--If results include IsResolvedCloning record, use that RequestSourceId below and the search value, otherwise use the ServiceRequestId

SELECT * FROM [coordinator].[ServiceRequest] WHERE Id IN (
SELECT ServiceRequestId FROM [coordinator].[LinkedRequestSource] WHERE RequestSourceType = 'IsResolvedCloning'
AND RequestSourceId = '702E388E-6DEE-4934-9F70-8075CB45FE67') --search value

--Keep the Active clone that is the most recent and cancel the others using the script below by ServiceRequestId from the above result set.

UPDATE [coordinator].[ServiceRequest] SET [Status] = 'Complete', [CompletionReason] = 'Canceled', [ModifiedDate] = SYSUTCDATETIME() WHERE Id = '01335151-2092-4AF6-8AAD-1950D46B4A97'