Differences

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

--- resolution_area:prometheus_resolutions:res-p9126 [2023/03/06 16:55] – aryan
+++ resolution_area:prometheus_resolutions:res-p9126 [2023/05/26 16:24] (current) – aryan
@@ Line 1: / Line 1: @@
-=====SalesForceNoForceMajeureFor7Days=====
+=====SalesForceNoForceMajeureForManyDays=====
 **Level:** Critical
-**Purpose:** Notify ATC team that SalesForce has not sent a Force Majeure for 7 days.
+**Purpose:** Notify ATC team that SalesForce has not sent a Force Majeure for Many days.
 **Scenario:** Due to the new customer-focused methodology that was introduced to SalesForce in 2023, more customer interaction is required by SalesForce. This means that if we do not receive CUs (Carrier Update) or FMs (Force Majeure) from them, it might become a problem for SalesForce as they are not receiving anything from their customers.
+/May/23 - Many was updated from 7 to 21 days
@@ Line 18: / Line 20: @@
 **Auto Clear:** Will clear when we receive a FM.
+** Cautionary Advisory Notice **
+Using Enigma [[http://logsearch.errigal.com|Kibana Log search]] to verify the logs is misleading, as we receive multiple updates post the initial FM setting. We only count the first/initial setting of the ticket to FM, not each update.
+Else pop onto atcapps1 and run
+<code>
+ zgrep -l  "Force_Majeure__c=true" ticketer-integration.log*
+</code>

Internal Errigal Collaboration Wiki