Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace: • remoteticketfailedtocreate_-_rabbitmq • res-p9114 • res-p9126
resolution_area:prometheus_resolutions:res-p9114

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
resolution_area:prometheus_resolutions:res-p9114 [2023/04/26 17:00] – 10.91.110.100resolution_area:prometheus_resolutions:res-p9114 [2023/09/04 17:13] (current) – 10.91.120.100
Line 19: Line 19:
  
 For ATC For ATC
-<code>curl --request POST -i -u '<USERNAME>':'<PASSWORD>' http://atcwatchdog.com/Ticketer/api/v1/integration/salesforce/link/<TICKET-ID></code>+<code>curl --request POST -i -u '<USERNAME>':'<PASSWORD>' https://atcwatchdog.com/Ticketer/api/v1/integration/salesforce/link/<TICKET-ID></code>
  
 The username and password is any username or password that has ticketer access on that environment. The username and password is any username or password that has ticketer access on that environment.
Line 48: Line 48:
         and (parent.name != 'ORPHANS' and grandparent.name != 'ORPHANS');         and (parent.name != 'ORPHANS' and grandparent.name != 'ORPHANS');
  
-To fix the problem you will have to requeue the dropped messages +<del>To fix the problem you will have to requeue the dropped messages 
-Here is a template for this request. +Here is a template for this request. NOTE: Troubleshooting steps at bottom are best tried first
     {     {
         "event_type": "PostInsert",         "event_type": "PostInsert",
Line 56: Line 56:
         "Due_Date__c": null,         "Due_Date__c": null,
         "SLA_Date__c": null,         "SLA_Date__c": null,
-        "Originating_System_ID__c": "ERRIGALTICKET"+        "Originating_System_ID__c": "ERRIGALTICKET",
         "Description": " ",         "Description": " ",
         "Alarm_Start_Date__c": "",         "Alarm_Start_Date__c": "",
Line 78: Line 78:
   - Rerun the query to double check that the Salesforce has a case for the Ticket.    - Rerun the query to double check that the Salesforce has a case for the Ticket. 
  
-For more details, please check this. https://docs.google.com/document/d/1_zwi02B8WoysEUEzfIK2A046xsmFfnrYqiaO4kA7QHk/edit#heading=h.z4rx22cg5uw8+For more details, please check this. https://docs.google.com/document/d/1_zwi02B8WoysEUEzfIK2A046xsmFfnrYqiaO4kA7QHk/edit#heading=h.z4rx22cg5uw8</del>
  
 ====Troubleshooting==== ====Troubleshooting====
Line 101: Line 101:
 2022-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"}] 2022-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> </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 **Auto Clear:** Yes, Alert will clear when the count of ATC DAS ticket was not created in Salesforce is 0
resolution_area/prometheus_resolutions/res-p9114.1682524834.txt.gz · Last modified: 2023/04/26 17:00 by 10.91.110.100

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki