<?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 Reruning playbook and preventing communication tasks from being rerun in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/reruning-playbook-and-preventing-communication-tasks-from-being/m-p/564415#M2804</link>
    <description>&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;I have been working on the XSOAR Platform for a long time and there is something which I haven't been able to find a solution for.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would like to rerun a playbook for multiple incidents and I use the !setPlaybook to do this. I do this after rectifying the issue on the playbook for example task error or similar. The problem is that many playbooks we are working with have a communication task such as Ask User or a Slack notification.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a way to rerun the playbook and prevent the communication tasks from running?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As you can understand this can be an issue especially if the incident is not so recent therefore the communication task would be superfluous. I understand that you can re-run a stopped-on error task yet this can cause the same problem because it will reach the communication stage.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would be interested to know if there is a way to tag or cause the communications tasks to skip only during this rerun.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks.&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Cortex XSOAR" id="Cortex_XSOAR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 05 Nov 2023 12:48:29 GMT</pubDate>
    <dc:creator>michaelsysec242</dc:creator>
    <dc:date>2023-11-05T12:48:29Z</dc:date>
    <item>
      <title>Reruning playbook and preventing communication tasks from being rerun</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/reruning-playbook-and-preventing-communication-tasks-from-being/m-p/564415#M2804</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;I have been working on the XSOAR Platform for a long time and there is something which I haven't been able to find a solution for.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would like to rerun a playbook for multiple incidents and I use the !setPlaybook to do this. I do this after rectifying the issue on the playbook for example task error or similar. The problem is that many playbooks we are working with have a communication task such as Ask User or a Slack notification.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a way to rerun the playbook and prevent the communication tasks from running?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As you can understand this can be an issue especially if the incident is not so recent therefore the communication task would be superfluous. I understand that you can re-run a stopped-on error task yet this can cause the same problem because it will reach the communication stage.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would be interested to know if there is a way to tag or cause the communications tasks to skip only during this rerun.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks.&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Cortex XSOAR" id="Cortex_XSOAR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 12:48:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/reruning-playbook-and-preventing-communication-tasks-from-being/m-p/564415#M2804</guid>
      <dc:creator>michaelsysec242</dc:creator>
      <dc:date>2023-11-05T12:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Reruning playbook and preventing communication tasks from being rerun</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/reruning-playbook-and-preventing-communication-tasks-from-being/m-p/564632#M2811</link>
      <description>&lt;P&gt;One way I can think of is have the communication task set a value into Context using the Set automation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then add a conditional in front of your DC tasks that checks whether that Key is set, and bypass the task if so.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On the first run it will work, on the following runs it will skip them.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 15:25:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/reruning-playbook-and-preventing-communication-tasks-from-being/m-p/564632#M2811</guid>
      <dc:creator>MBeauchamp2</dc:creator>
      <dc:date>2023-11-07T15:25:26Z</dc:date>
    </item>
    <item>
      <title>Re: Reruning playbook and preventing communication tasks from being rerun</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/reruning-playbook-and-preventing-communication-tasks-from-being/m-p/565257#M2821</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/159920"&gt;@MBeauchamp2&lt;/a&gt;&amp;nbsp;, Thanks for the insight. It is possible that I can add this flow for all playbooks no matter how laborious it is. It is a shame that there is not way to manage communication tasks from an overview level. I could look into a feature request.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I will mark your answer as a solution even though it is more of a workaround.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 12 Nov 2023 09:53:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/reruning-playbook-and-preventing-communication-tasks-from-being/m-p/565257#M2821</guid>
      <dc:creator>michaelsysec242</dc:creator>
      <dc:date>2023-11-12T09:53:43Z</dc:date>
    </item>
  </channel>
</rss>

