Body: <p>I upgraded to 5.64.2 on WordPress 6.3.1 yesterday and since then I'm seeing scheduled job failures. There's no error showing in the logs in ConfigAndLog but this is appearing next to each scheduled job:</p>
  <pre><code>Entity: Job Action: send_reminder
  Summary
  Finished execution of Send Scheduled Reminders with result: Failure, Error message: DB Error: no such field
  Details
  
  Parameters parsed (and passed to API method): 
  a:1:{s:7:&quot;version&quot;;i:3;}
  
  Full message: 
  Finished execution of Send Scheduled Reminders with result: Failure, Error message: DB Error: no such field
  
  </code></pre>
  <p>If I run the job manually it works fine, but when it's triggered from cron it seems to be failing. Is there anything I can do to debug what's happening here?</p>
  <p>Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-08-30T12:26:58.783Z
Comments.Text: Maybe a permissions problem when run as cron? How are you running cron?
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-08-30T16:01:48.730Z
Comments.Text: I had a similar problem after upgrading to 5.63.3, but on Drupal. Cron stopped working, and the fix (I think, not 100% sure) was to unblock the cron user.  In Drupal you can block a user, and up to now this has been a good way to have a user that works in cron but cannot login.  Maybe there was a change in Civi so blocked users cannot  be used in this situation? Anyway, I unblocked the user & cron worked again.
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-08-30T19:52:51.207Z
Comments.Text: See my earlier comment - I tested again on a 5.64.1 system & confirm that a user for cron who is blocked will stop cron working.  This is on a Drupal 7 & there's a message in the Drupal log 'Exception: Sorry, can not load CMS user account. in CRM_Utils_System_Drupal->loadBootStrap() (line 549 of /home/acivior1/public_html/sites/all/modules/civicrm/CRM/Utils/System/Drupal.php).'  A change must have been made sometime after 5.58.  If this fixes your problem please let me know and I'll make it the answer.
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-09-07T13:30:51.207Z
Comments.Text: What's strange is that other cron jobs are running fine (including scheduled mailings) - it's just this one that doesn't run
Comments.UserDisplayName: christodhunter
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-09-18T10:38:29.350Z
Comments.Text: I've tried running the cron job as a super admin user and it fires fine. I suspect there's a deprecated merge tag in a reminder somewhere as it doesn't always fail. Is there a way to dig into which reminders were attempted to be sent?
Comments.UserDisplayName: christodhunter
Tags: <scheduled-reminders>
Title: Scheduled job (send_reminder) failing since upgrading to 5.64.2
ThreadText: # Scheduled job (send_reminder) failing since upgrading to 5.64.2
  
  (Asked by: username_0 on 2023-08-30)
  
  I upgraded to 5.64.2 on WordPress 6.3.1 yesterday and since then I'm seeing scheduled job failures. There's no error showing in the logs in ConfigAndLog but this is appearing next to each scheduled job:
  
  ```
  Entity: Job Action: send_reminder
  Summary
  Finished execution of Send Scheduled Reminders with result: Failure, Error message: DB Error: no such field
  Details
  
  Parameters parsed (and passed to API method): 
  a:1:{s:7:"version";i:3;}
  
  Full message: 
  Finished execution of Send Scheduled Reminders with result: Failure, Error message: DB Error: no such field
  
  ```
  
  If I run the job manually it works fine, but when it's triggered from cron it seems to be failing. Is there anything I can do to debug what's happening here?
  
  Thanks!
  
  **Tags:** scheduled-reminders
  
  > **Comments:**
  > **username_1**: Maybe a permissions problem when run as cron? How are you running cron?  
  > **username_2**: I had a similar problem after upgrading to 5.63.3, but on Drupal. Cron stopped working, and the fix (I think, not 100% sure) was to unblock the cron user.  In Drupal you can block a user, and up to now this has been a good way to have a user that works in cron but cannot login.  Maybe there was a change in Civi so blocked users cannot  be used in this situation? Anyway, I unblocked the user & cron worked again.  
  > **username_2**: See my earlier comment - I tested again on a 5.64.1 system & confirm that a user for cron who is blocked will stop cron working.  This is on a Drupal 7 & there's a message in the Drupal log 'Exception: Sorry, can not load CMS user account. in CRM_Utils_System_Drupal->loadBootStrap() (line 549 of /home/acivior1/public_html/sites/all/modules/civicrm/CRM/Utils/System/Drupal.php).'  A change must have been made sometime after 5.58.  If this fixes your problem please let me know and I'll make it the answer.  
  > **username_0**: What's strange is that other cron jobs are running fine (including scheduled mailings) - it's just this one that doesn't run  
  > **username_0**: I've tried running the cron job as a super admin user and it fires fine. I suspect there's a deprecated merge tag in a reminder somewhere as it doesn't always fail. Is there a way to dig into which reminders were attempted to be sent?  
  
  ---
  
  ## 0 answers
  
  