<?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 SubAtomic API Output Manager Limit in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/subatomic-api-output-manager-limit/m-p/532441#M4458</link>
    <description>&lt;P&gt;Hi, I have just tried to use the Expedition "API Output Manager" for the first time and find some rather strange behaviour.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have used ML to create around 33 new security rules, when I went to the&amp;nbsp;"API Output Manager" to generate api commands for each rule (SubAtomic) I selected all the api calls for the security rules and pushed to the firewall, after commiting this and coming back a day later, I notice some traffic is hitting my catchall rule (at the bottom) for which I know I created rules for.&amp;nbsp; Further investiagtion I realised that there were only around 22 rules created by the&amp;nbsp;"API Output Manager" so the last 11 rules never had API commands generated for them, I tried regenerating the API calls again in expedition but still only 22 rules create.&amp;nbsp; I moved the bottom 11 rules to the top of the rulebase in expedition and generated the API commands again in&amp;nbsp;"API Output Manager" and although only 22 rules were created again the previously excluded rules (now at the top) were present.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This feels like a limit on the subatomic API output, obviously there were a lot of other API calls generated I didn't use but is anyone aware of a limit on this output, also when using atomic all the rules are listed correctly so it seems to me there isn't an issue with the rules themselves.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Feb 2023 10:10:05 GMT</pubDate>
    <dc:creator>ChrisHammock</dc:creator>
    <dc:date>2023-02-28T10:10:05Z</dc:date>
    <item>
      <title>SubAtomic API Output Manager Limit</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/subatomic-api-output-manager-limit/m-p/532441#M4458</link>
      <description>&lt;P&gt;Hi, I have just tried to use the Expedition "API Output Manager" for the first time and find some rather strange behaviour.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have used ML to create around 33 new security rules, when I went to the&amp;nbsp;"API Output Manager" to generate api commands for each rule (SubAtomic) I selected all the api calls for the security rules and pushed to the firewall, after commiting this and coming back a day later, I notice some traffic is hitting my catchall rule (at the bottom) for which I know I created rules for.&amp;nbsp; Further investiagtion I realised that there were only around 22 rules created by the&amp;nbsp;"API Output Manager" so the last 11 rules never had API commands generated for them, I tried regenerating the API calls again in expedition but still only 22 rules create.&amp;nbsp; I moved the bottom 11 rules to the top of the rulebase in expedition and generated the API commands again in&amp;nbsp;"API Output Manager" and although only 22 rules were created again the previously excluded rules (now at the top) were present.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This feels like a limit on the subatomic API output, obviously there were a lot of other API calls generated I didn't use but is anyone aware of a limit on this output, also when using atomic all the rules are listed correctly so it seems to me there isn't an issue with the rules themselves.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2023 10:10:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/subatomic-api-output-manager-limit/m-p/532441#M4458</guid>
      <dc:creator>ChrisHammock</dc:creator>
      <dc:date>2023-02-28T10:10:05Z</dc:date>
    </item>
  </channel>
</rss>

