Body: <p>We have setup the automated Cron job to run on the server every 15 minutes. This works great for newsletters and other jobs. However when it comes to the membership status job it always fails after running partially. I just get a error 500 from the server. We are trying to identify if it could be due to a particular membership type, membership record or CiviCRM. </p>
  
  <p>We have updated CiviCRM a couple of times and the it is on the most stable long term versions i.e. 4.6.38 and Drupal 7.6x. </p>
  
  <ol>
  <li>Has anyone come across this error?</li>
  <li>In the command parameters can we add a command to run only by certain membership types? Does anyone know what this command will be? This way we can debug the issue in more detail. </li>
  </ol>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-18T13:37:34.143Z
Comments.Text: How many members do you have?
Comments.UserDisplayName: Tony Horrocks
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-19T10:17:06.450Z
Comments.Text: Is there anything useful in the CiviCRM log file?  Typically under `sites/default/files/civicrm/ConfigAndLog`
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-25T23:36:29.300Z
Comments.Text: There are about 5000 Members and 35K contacts. Can't find anything in the log files. It just shows an error 500. Any other ideas? Thanks.
Comments.UserDisplayName: Sohal Khatwani
Tags: <civimember><cron-job>
Title: Automatic Membership Status Jobs Fails on Cron Run
ThreadText: # Automatic Membership Status Jobs Fails on Cron Run
  
  (Asked by: username_0 on 2018-11-18)
  
  We have setup the automated Cron job to run on the server every 15 minutes. This works great for newsletters and other jobs. However when it comes to the membership status job it always fails after running partially. I just get a error 500 from the server. We are trying to identify if it could be due to a particular membership type, membership record or CiviCRM.
  
  We have updated CiviCRM a couple of times and the it is on the most stable long term versions i.e. 4.6.38 and Drupal 7.6x.
  
  1. Has anyone come across this error?
  2. In the command parameters can we add a command to run only by certain membership types? Does anyone know what this command will be? This way we can debug the issue in more detail.
  
  **Tags:** civimember, cron-job
  
  > **Comments:**
  > **username_1**: How many members do you have?  
  > **username_2**: Is there anything useful in the CiviCRM log file?  Typically under `sites/default/files/civicrm/ConfigAndLog`  
  > **username_0**: There are about 5000 Members and 35K contacts. Can't find anything in the log files. It just shows an error 500. Any other ideas? Thanks.  
  
  ---
  
  ## 0 answers
  
  