<?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: A commit is in progress. Please try again later in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/a-commit-is-in-progress-please-try-again-later/m-p/1234721#M6130</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/37508"&gt;@JimMcGrady&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please check the reason for auto-commit failure and based on error you can proceed further to troubleshoot the issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding disabling Auto-commit- yes auto-commit can be disabled from root but you have to work with Palo Alto TAC, you can't disable without tac.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Jul 2025 18:16:29 GMT</pubDate>
    <dc:creator>mshekh</dc:creator>
    <dc:date>2025-07-25T18:16:29Z</dc:date>
    <item>
      <title>A commit is in progress. Please try again later</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/a-commit-is-in-progress-please-try-again-later/m-p/1234684#M6127</link>
      <description>&lt;P&gt;Running 10.2.13 on a PA-440. Current config issues mean a commit fails. The unit keeps trying to auto commit very frequently (which fails).&lt;/P&gt;
&lt;P&gt;If i try to change the config and commit, i get the message "A commit is in progress. Please try again later". If i try to install a different software version i get the same error. How can i disable auto commit?&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jul 2025 07:24:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/a-commit-is-in-progress-please-try-again-later/m-p/1234684#M6127</guid>
      <dc:creator>JimMcGrady</dc:creator>
      <dc:date>2025-07-25T07:24:16Z</dc:date>
    </item>
    <item>
      <title>Re: A commit is in progress. Please try again later</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/a-commit-is-in-progress-please-try-again-later/m-p/1234721#M6130</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/37508"&gt;@JimMcGrady&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please check the reason for auto-commit failure and based on error you can proceed further to troubleshoot the issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding disabling Auto-commit- yes auto-commit can be disabled from root but you have to work with Palo Alto TAC, you can't disable without tac.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jul 2025 18:16:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/a-commit-is-in-progress-please-try-again-later/m-p/1234721#M6130</guid>
      <dc:creator>mshekh</dc:creator>
      <dc:date>2025-07-25T18:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: A commit is in progress. Please try again later</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/a-commit-is-in-progress-please-try-again-later/m-p/1234779#M6134</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;An "A commit is in progress" message on your Palo Alto Networks PA-440, especially with frequent failed auto-commits, indicates a stuck commit process. While there isn't a direct "disable auto-commit" setting in the typical sense for ongoing config changes, you need to clear the hung commit job. First, use show jobs all on the CLI to identify the stuck commit job ID. Then, attempt to clear it with clear job id &amp;lt;job_id&amp;gt;. If the issue persists, a common resolution is to restart the management plane processes using debug software restart process management-server and debug software restart process device-server. However, be aware that restarting management services will temporarily disrupt management access to the firewall. If these steps don't resolve the issue, contacting Palo Alto Networks TAC is recommended, as deeper issues like memory problems or specific software bugs might be involved, especially with 10.2.13.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2025 10:18:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/a-commit-is-in-progress-please-try-again-later/m-p/1234779#M6134</guid>
      <dc:creator>alison23taylor</dc:creator>
      <dc:date>2025-07-28T10:18:35Z</dc:date>
    </item>
  </channel>
</rss>

