Answers.Body: <p>You'll probably find an error in <a href="https://civicrm.stackexchange.com/questions/15931/where-are-the-configandlog-and-templates-c-directories">ConfigAndLog</a>. If not, it does a cache clear (several times actually) after that so maybe it's just slow. Or, you can turn on backtrace under admin - system settings - debugging, and then open the browser console network tab while doing the upgrade. If it's crashing you'll see an error 500, and you can click on the response subtab to see the stacktrace.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-07-12T15:51:54.070Z
Answers.LastActivityDate: 2024-07-12T15:51:54.070Z
Answers.UserDisplayName: Demerit
Body: <p>In all recent upgrades of CiviCRM Wordpress (to 5.71.x, 5.72.x and 5.73.0), the DB upgrade process executing URL</p>
  <pre><code>https://&lt;mysite&gt;/wp-admin/admin.php?page=CiviCRM&amp;q=civicrm%2Fupgrade%2Fqueue%2Frunner&amp;reset=1&amp;qrid=CRM_Upgrade
  </code></pre>
  <p>freezes on message [Executed: Update all reserved message templates].</p>
  <p>Issuing again the URL above solves the problem, but I wonder why I need to issue this URL twice. I am using Firefox as browser.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-05-03T18:33:29.030Z
Comments.Text: You'll probably find an error in [ConfigAndLog](https://civicrm.stackexchange.com/questions/15931/where-are-the-configandlog-and-templates-c-directories). If not, it does a cache clear (several times actually) after that so maybe it's just slow. Or, you can turn on backtrace under admin - system settings - debugging, and then open the browser console network tab while doing the upgrade. If it's crashing you'll see an error 500, and you can click on the response subtab to see the stacktrace.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-07-12T15:05:55.867Z
Comments.Text: @Demerit Would it make sense to enter your comment as an answer, as it seems to be one, and a good one at that?
Comments.UserDisplayName: guyiac
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-07-12T15:51:49.743Z
Comments.Text: Thanks. Sure why not.
Comments.UserDisplayName: Demerit
Tags: <upgrade>
Title: Why does DB upgrade freeze on message "Executed: Update all reserved message templates"?
ThreadText: # Why does DB upgrade freeze on message "Executed: Update all reserved message templates"?
  
  (Asked by: username_0 on 2024-05-03)
  
  In all recent upgrades of CiviCRM Wordpress (to 5.71.x, 5.72.x and 5.73.0), the DB upgrade process executing URL
  
  ```
  https://<mysite>/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fupgrade%2Fqueue%2Frunner&reset=1&qrid=CRM_Upgrade
  
  ```
  
  freezes on message [Executed: Update all reserved message templates].
  
  Issuing again the URL above solves the problem, but I wonder why I need to issue this URL twice. I am using Firefox as browser.
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: You'll probably find an error in [ConfigAndLog](https://civicrm.stackexchange.com/questions/15931/where-are-the-configandlog-and-templates-c-directories). If not, it does a cache clear (several times actually) after that so maybe it's just slow. Or, you can turn on backtrace under admin - system settings - debugging, and then open the browser console network tab while doing the upgrade. If it's crashing you'll see an error 500, and you can click on the response subtab to see the stacktrace.  
  > **username_2**: @username_1 Would it make sense to enter your comment as an answer, as it seems to be one, and a good one at that?  
  > **username_1**: Thanks. Sure why not.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-07-12. Score: 0
  
  You'll probably find an error in [ConfigAndLog](https://civicrm.stackexchange.com/questions/15931/where-are-the-configandlog-and-templates-c-directories). If not, it does a cache clear (several times actually) after that so maybe it's just slow. Or, you can turn on backtrace under admin - system settings - debugging, and then open the browser console network tab while doing the upgrade. If it's crashing you'll see an error 500, and you can click on the response subtab to see the stacktrace.
  
  
  ---
  
  