Answers.Body: <p>As per the code, retry and skip seems to be shown with the value set for debug. Note <code>Enable Debugging</code> if it is turned on/off on <code>Administer-&gt; System Settings -&gt; Debugging and Error Handling</code>.</p>
  
  <p>Need to confirm this on another upgrade I do, but for now, it seems retry and skip <a href="https://github.com/jitendrapurohit/civicrm-core/blob/master/CRM/Upgrade/Page/Upgrade.php#L163" rel="nofollow noreferrer">would show up if debugging is enabled</a> and the upgrade would progress only after <a href="https://github.com/jitendrapurohit/civicrm-core/blob/master/templates//CRM/Queue/Page/Runner.tpl#L128" rel="nofollow noreferrer">Retry button is clicked</a>. So for continuous upgrade, one should have <code>debug</code> set to <code>No</code>?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-31T22:26:38.243Z
Answers.Text: is it worth thinking about having a msg pop up at /upgrade to say 'you have debug enabled'?
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-03T01:00:40.160Z
Answers.Text: It happens to me too. I can see how I get an error to the console with PHP notice and warnings printed on a json response. What's strange is that I initially have all debug modes turned off.
Answers.UserDisplayName: Francesc Bassas i Bullich
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-03T01:10:31.070Z
Answers.Text: **Notice**: Undefined index: CRM_Upgrade in (...)/civicrm/CRM/Queue/Service.php on line 131
  
   **Warning**: file_get_contents(): Filename cannot be empty in (...)/civicrm/CRM/Upgrade/Form.php on line 722
  
  **Warning**: file_put_contents(): Filename cannot be empty in (...)/civicrm/CRM/Upgrade/Form.php on line 724
  {"is_error":0,"exception":null,"last_task_title":"Upgrade DB to 4.7.19","numberOfItems":"17","is_continue":1}
Answers.UserDisplayName: Francesc Bassas i Bullich
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-26T21:09:36.587Z
Answers.Text: Disabling display_errors at server side finally solved it for me.
Answers.UserDisplayName: Francesc Bassas i Bullich
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-31T12:23:57.213Z
Answers.LastActivityDate: 2017-07-31T12:23:57.213Z
Answers.UserDisplayName: jitendra - fuzion
Body: <p>Not used to seeing this but one site just stopped at each step of the journey.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-31T09:32:09.543Z
Comments.Text: I have seen this happen when the previous drupal/ module folder can still be found.
Comments.UserDisplayName: Seamus Lee
Tags: <upgrade>
Title: Why does the civicrm upgrade stop after each step of the upgrade eg at 4.7.19 then again at 4.7.20
ThreadText: # Why does the civicrm upgrade stop after each step of the upgrade eg at 4.7.19 then again at 4.7.20
  
  (Asked by: username_0 on 2017-07-31)
  
  Not used to seeing this but one site just stopped at each step of the journey.
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: I have seen this happen when the previous drupal/ module folder can still be found.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-07-31. Score: 3 | Accepted answer
  
  As per the code, retry and skip seems to be shown with the value set for debug. Note `Enable Debugging` if it is turned on/off on `Administer-> System Settings -> Debugging and Error Handling`.
  
  Need to confirm this on another upgrade I do, but for now, it seems retry and skip [would show up if debugging is enabled](https://github.com/jitendrapurohit/civicrm-core/blob/master/CRM/Upgrade/Page/Upgrade.php#L163) and the upgrade would progress only after [Retry button is clicked](https://github.com/jitendrapurohit/civicrm-core/blob/master/templates//CRM/Queue/Page/Runner.tpl#L128). So for continuous upgrade, one should have `debug` set to `No`?
  
  > **Comments:**
  > **username_0**: is it worth thinking about having a msg pop up at /upgrade to say 'you have debug enabled'?  
  > **username_3**: It happens to me too. I can see how I get an error to the console with PHP notice and warnings printed on a json response. What's strange is that I initially have all debug modes turned off.  
  > **username_3**: **Notice**: Undefined index: CRM_Upgrade in (...)/civicrm/CRM/Queue/Service.php on line 131   **Warning**: file_get_contents(): Filename cannot be empty in (...)/civicrm/CRM/Upgrade/Form.php on line 722  **Warning**: file_put_contents(): Filename cannot be empty in (...)/civicrm/CRM/Upgrade/Form.php on line 724 {"is_error":0,"exception":null,"last_task_title":"Upgrade DB to 4.7.19","numberOfItems":"17","is_continue":1}  
  > **username_3**: Disabling display_errors at server side finally solved it for me.  
  
  ---
  
  