<?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: Polling job for search results, not just search completion in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/polling-job-for-search-results-not-just-search-completion/m-p/450028#M441</link>
    <description>&lt;P&gt;I received an answer from my resident engineer.&amp;nbsp; The&amp;nbsp;&lt;SPAN&gt;QRadarFullSearch sub-playbook that&amp;nbsp;I'm calling can be set up with a built-in loop to check for the presence of results.&amp;nbsp; After the playbook finishes (meaning the search has completed) it can be repeated if no results were found, with X number of seconds between runs and up to N number of retries.&amp;nbsp; I've only ever used the 'for-each input' loop criterion...I didn't realize you could make it so much smarter!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I continue to be amazed every day at the things XSOAR can do.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Nov 2021 14:45:45 GMT</pubDate>
    <dc:creator>Jeff.McGurk</dc:creator>
    <dc:date>2021-11-29T14:45:45Z</dc:date>
    <item>
      <title>Polling job for search results, not just search completion</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/polling-job-for-search-results-not-just-search-completion/m-p/449266#M438</link>
      <description>&lt;P&gt;I'd like to take the generic polling concept and make it a little more specific, but I'm coming up short.&amp;nbsp; I'm doing a QRadar search (although I suspect Splunk or anything else would be very similar.)&amp;nbsp; The QRadarFullSearch playbook will poll and wait for the search to finish, and that has worked great so far for what it is.&amp;nbsp; But the search can finish while not actually finding anything.&amp;nbsp; Can I somehow set some loops and polling to do the search, check for results, and then kick off a new search if no results were found?&amp;nbsp; I would still like to use the timeout value so I'm not creating an infinite loop situation.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Nov 2021 16:27:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/polling-job-for-search-results-not-just-search-completion/m-p/449266#M438</guid>
      <dc:creator>Jeff.McGurk</dc:creator>
      <dc:date>2021-11-24T16:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: Polling job for search results, not just search completion</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/polling-job-for-search-results-not-just-search-completion/m-p/449293#M439</link>
      <description>&lt;P&gt;This could be done in a Playbook, or, study teh code in QRadar and create an automation script "wrapper" for the command. In essence, the script would perform the search and return a ScheduledCommand object. This causes it to re-schedule for the next run and when you finally do receive the results (or lack there of) you could optionally change the search criteria and perform the same script again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you kept the option to achieve this in an automation script, the ScheduledCommand can be used (even with altered arguments) and be kept within your first defined timeout.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Nov 2021 18:26:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/polling-job-for-search-results-not-just-search-completion/m-p/449293#M439</guid>
      <dc:creator>ABurt</dc:creator>
      <dc:date>2021-11-24T18:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: Polling job for search results, not just search completion</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/polling-job-for-search-results-not-just-search-completion/m-p/450028#M441</link>
      <description>&lt;P&gt;I received an answer from my resident engineer.&amp;nbsp; The&amp;nbsp;&lt;SPAN&gt;QRadarFullSearch sub-playbook that&amp;nbsp;I'm calling can be set up with a built-in loop to check for the presence of results.&amp;nbsp; After the playbook finishes (meaning the search has completed) it can be repeated if no results were found, with X number of seconds between runs and up to N number of retries.&amp;nbsp; I've only ever used the 'for-each input' loop criterion...I didn't realize you could make it so much smarter!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I continue to be amazed every day at the things XSOAR can do.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 14:45:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/polling-job-for-search-results-not-just-search-completion/m-p/450028#M441</guid>
      <dc:creator>Jeff.McGurk</dc:creator>
      <dc:date>2021-11-29T14:45:45Z</dc:date>
    </item>
  </channel>
</rss>

