Email Re-Opening Closed Incidents -Solution = Execution Order

KKrabbenhoft
Tera Guru

All, 

First Kudos to @jimbeam5 , @Alikutty A for getting me on the right track. A review of the script that was provided here. allowed me to determine if any changes were made during the upgrade to Xanadu. 

Things just got moved around but ultimately work the same. 
Then, using gs.log with the help of Dylan Hutchens my manager, it was determined that the inbound action "Update Incident (BP)" was not even being triggered.
For those who are not familiar with this inbound email action, it allows for an email reply from the "Incident closed" notification to set the resolved state of an incident to "In Progress" as long as the words "please reopen" are added to the subject line. It also comments the incident. 

Here's a refined summary:

The **"Update Incident (BP)"** inbound email action wasn’t reopening incidents in a resolved state because it was not executing. The root cause was its **execution order set to 100**, which matched another inbound action, creating an unpredictable execution sequence. This action specifically requires the **subject line to contain "please reopen"** when replying. After adjusting the execution order from **100 to 99**, this action now runs first, successfully processing replies and reopening incidents by setting their state to **In Progress**.


I hope this helps someone else as much as it did me. 
 

0 REPLIES 0