<?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 How to stop a playbook task until ALL previous tasks are done? in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-stop-a-playbook-task-until-all-previous-tasks-are-done/m-p/598771#M3640</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm developing a playbook for &lt;LI-PRODUCT title="Cortex XSOAR" id="Cortex_XSOAR"&gt;&lt;/LI-PRODUCT&gt; that sends a number of queries to our SIEM in parallel and uploads the results as files to an incident. I want to introduce subsequent steps that all depend on the files existing, however I cannot figure out a good to make a "gate" task that stops the playbook from executing until all previously linked tasks are done OR errored out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the "second stage" ran before all queries were completed, even if they return successfully, their data wouldn't be picked up by the later steps. If there's something obvious in the built-ins I'm missing, please do let me know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best!&lt;/P&gt;</description>
    <pubDate>Wed, 25 Sep 2024 16:51:31 GMT</pubDate>
    <dc:creator>T.Jagielski</dc:creator>
    <dc:date>2024-09-25T16:51:31Z</dc:date>
    <item>
      <title>How to stop a playbook task until ALL previous tasks are done?</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-stop-a-playbook-task-until-all-previous-tasks-are-done/m-p/598771#M3640</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm developing a playbook for &lt;LI-PRODUCT title="Cortex XSOAR" id="Cortex_XSOAR"&gt;&lt;/LI-PRODUCT&gt; that sends a number of queries to our SIEM in parallel and uploads the results as files to an incident. I want to introduce subsequent steps that all depend on the files existing, however I cannot figure out a good to make a "gate" task that stops the playbook from executing until all previously linked tasks are done OR errored out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the "second stage" ran before all queries were completed, even if they return successfully, their data wouldn't be picked up by the later steps. If there's something obvious in the built-ins I'm missing, please do let me know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best!&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 16:51:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-stop-a-playbook-task-until-all-previous-tasks-are-done/m-p/598771#M3640</guid>
      <dc:creator>T.Jagielski</dc:creator>
      <dc:date>2024-09-25T16:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop a playbook task until ALL previous tasks are done?</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-stop-a-playbook-task-until-all-previous-tasks-are-done/m-p/598775#M3643</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could write a conditional that checks all the context data entries exist before continuing with the playbook execution.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 17:22:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-stop-a-playbook-task-until-all-previous-tasks-are-done/m-p/598775#M3643</guid>
      <dc:creator>Ivetto</dc:creator>
      <dc:date>2024-09-25T17:22:42Z</dc:date>
    </item>
  </channel>
</rss>

