Differences

This shows you the differences between two versions of the page.

--- resolution_area:prometheus_resolutions:res-p9114 [2023/06/09 15:35] – 10.91.110.100
+++ resolution_area:prometheus_resolutions:res-p9114 [2023/09/04 17:13] (current) – 10.91.120.100
@@ Line 101: / Line 101: @@
 -09-28 10:11:16.149  INFO 25776 --- [SalesforceHttpClient@44be69aa-42] org.apache.camel.Tracing                 :      [route11     ] [rabbitmq://{{rabbitmq.queues.sale] Exchange[Id: 7B60355912D6F25-000000000000EC78, BodyType: byte[], Body: {"Status":"New","Carrier_Update__c":null,"Force_Majeure__c":false,"CaseNumber":"02475388","CN_Priority__c":"4","Id":"5003g00000N6Z0TAAV","Originating_System_ID__c":"764517","correlationId":"bf2d5435-abed-4f0e-aa40-01fb8aa30cff"}]
 </code>
+If the ticketer-integration logs are showing that the ticket already exists in salesforce, (i.e. you are getting ""error":"duplicate value found: Originating_System_ID__c duplicates value on record with id") and the RabbitMQ re-queue is not working. Then its safe to just add entries into the ticketer.external_source table yourself. Just put in the salesforce case number, saleforce case ID and ticketer ticket id where appropriate (duplicate the three rows necessary and populate the info). This is only a good idea when the ticket already exists in ATCs salesforce.
 **Auto Clear:** Yes, Alert will clear when the count of ATC DAS ticket was not created in Salesforce is 0

Internal Errigal Collaboration Wiki