<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Close an incident when all the linked incidents are closed in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/close-an-incident-when-all-the-linked-incidents-are-closed/m-p/592253#M3470</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/966138513"&gt;@lordstark&lt;/a&gt;&amp;nbsp;– A post-processing script would've been my first suggestion for your use case. To deal with the risk of a race condition, you could use the&amp;nbsp;&lt;STRONG&gt;Demisto Lock&lt;/STRONG&gt; integration (call&amp;nbsp;&lt;STRONG&gt;demisto-lock-get&amp;nbsp;&lt;/STRONG&gt;and&amp;nbsp;&lt;STRONG&gt;demisto-lock-release&lt;/STRONG&gt; within the script) so only one incident's post-processing script can perform the check at a time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If that approach doesn't work, another idea is to periodically run a job to check the incidents and close them when all of their linked incidents are closed. However, a post-processing script would be preferable because it would be much more timely and efficient.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jul 2024 00:47:59 GMT</pubDate>
    <dc:creator>asawyer</dc:creator>
    <dc:date>2024-07-17T00:47:59Z</dc:date>
    <item>
      <title>Close an incident when all the linked incidents are closed</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/close-an-incident-when-all-the-linked-incidents-are-closed/m-p/592011#M3461</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I want to be able to close an incident when all the linked incidents (child incidents) are closed. Is there a way to achieve this without having to run a post processing script for each linked incident? Post processing scripts introduce a race condition when two automations check each other out for status at the same time.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2024 11:44:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/close-an-incident-when-all-the-linked-incidents-are-closed/m-p/592011#M3461</guid>
      <dc:creator>lordstark</dc:creator>
      <dc:date>2024-07-15T11:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Close an incident when all the linked incidents are closed</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/close-an-incident-when-all-the-linked-incidents-are-closed/m-p/592253#M3470</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/966138513"&gt;@lordstark&lt;/a&gt;&amp;nbsp;– A post-processing script would've been my first suggestion for your use case. To deal with the risk of a race condition, you could use the&amp;nbsp;&lt;STRONG&gt;Demisto Lock&lt;/STRONG&gt; integration (call&amp;nbsp;&lt;STRONG&gt;demisto-lock-get&amp;nbsp;&lt;/STRONG&gt;and&amp;nbsp;&lt;STRONG&gt;demisto-lock-release&lt;/STRONG&gt; within the script) so only one incident's post-processing script can perform the check at a time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If that approach doesn't work, another idea is to periodically run a job to check the incidents and close them when all of their linked incidents are closed. However, a post-processing script would be preferable because it would be much more timely and efficient.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2024 00:47:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/close-an-incident-when-all-the-linked-incidents-are-closed/m-p/592253#M3470</guid>
      <dc:creator>asawyer</dc:creator>
      <dc:date>2024-07-17T00:47:59Z</dc:date>
    </item>
  </channel>
</rss>

