Answers.Body: <p>It's hardcoded that it needs to be hourly or more: <a href="https://github.com/civicrm/civicrm-core/blob/69cd824e26fc6e90a88e6cf18d9d011c1c85b94e/CRM/Utils/Check/Component/Env.php#L317" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/blob/69cd824e26fc6e90a88e6cf18d9d011c1c85b94e/CRM/Utils/Check/Component/Env.php#L317</a></p>
  <p>And I'm pretty sure it's tracking the Job.execute job, not any individual job: <a href="https://github.com/civicrm/civicrm-core/blob/69cd824e26fc6e90a88e6cf18d9d011c1c85b94e/CRM/Core/JobManager.php#L72" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/blob/69cd824e26fc6e90a88e6cf18d9d011c1c85b94e/CRM/Core/JobManager.php#L72</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-06T16:19:27.000Z
Answers.Text: Yes, I get the same thing on any of my sites where we're not running the cron every hour (or more). A lot of ours are set to like every 3 hours or so, so we always have this error come up. I just told it to hide it or whatever so it wouldn't bug me.
Answers.UserDisplayName: Jenni Simonis
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-07T00:51:05.480Z
Answers.Text: I increased the frequency of version_check to every hour, but the message still appears. Clearly in my situation, only a manual job execution will satisfy the criteria to make this go away (and then only for an hour).  The last thing I want to do is start hacking into core functions when my PHP skills are basic.
Answers.UserDisplayName: Garry H
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-07T01:13:25.910Z
Answers.Text: Is there a reason you need separate cron jobs instead of running job.execute? I.e. just have one cron job with `-a execute` and enable the jobs at Admin - System Settings - Scheduled Jobs. You could still have individual jobs run separately in addition if you really want.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-07T03:20:47.073Z
Answers.Text: Aha.  I didn't fully understand the baffling cron documentation.  So the solution appears to be; 
  
  1. at Admin - System Settings - Scheduled Jobs, enable only jobs that don't require parameters (e.g. version_check, cleanup) and let job.execute manage their execution
  
  2. trigger jobs that require parameters separately
  
  I didn't realise (until I just tried it) that you can trigger jobs without them being enabled at Admin - System Settings - Scheduled Jobs. That's not mentioned anywhere.
  
  Thanks for your help! Problem solved.
Answers.UserDisplayName: Garry H
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-07T03:25:35.730Z
Answers.Text: Yes civi cron can be difficult to get going, especially the first time.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-05T20:22:58.180Z
Answers.LastActivityDate: 2021-12-05T20:22:58.180Z
Answers.UserDisplayName: Demerit
Body: <p>I've seen a couple of Drupal workarounds for this, but not for Wordpress.</p>
  <p>The CiviCRM status is below; note that the last reported cron run was manually executed by me.</p>
  <blockquote>
  <p>All extensions are up-to-date:
  CKEditor4: Version 5.43.0
  Contribution cancel actions: Version 5.43.0
  Event Cart: Version 5.43.0
  Financial ACLs: Version 5.43.0
  Theme: Greenwich: Version 5.43.0
  Custom search framework: Version 5.43.0
  reCAPTCHA: Version 5.43.0
  Sequential credit notes: Version 5.43.0</p>
  </blockquote>
  <blockquote>
  <p>PHP Up-to-Date
  This system uses PHP version 7.4.26 which meets or exceeds the recommendation of 7.3.</p>
  </blockquote>
  <blockquote>
  <p>Cron Not Running
  Last cron run at November 26th, 2021 2:35 PM.</p>
  </blockquote>
  <p>I have a separate Cron task for each Scheduled Job, specified on cPanel using the CLI method (because this works better than wget, and no other method worked for me). I can see all tasks are running as they should [Administer &gt; System Settings &gt; Scheduled Jobs], yet the &quot;Cron Not Running&quot; message still pops-up constantly too. This is really annoying.</p>
  <p>Here's an example of one of my cPanel Cron jobs, working as expected at 1AM daily (0 1 * * *)</p>
  <p><code>/usr/local/bin/ea-php74 /home/ACCOUNT/public_html/wp-content/plugins/civicrm/civicrm/bin/cli.php -s MYDOMAIN -j -u USERNAME -p PASSWORD -e job -a version_check &gt;/dev/null 2&gt;&amp;1</code></p>
  <p>So what triggers this Cron error message? I have set job=version_check to run only once a day, yet it suggests more frequently - &quot;CiviCRM Update Check (Always)&quot;. How can you &quot;always&quot; run a periodic job? Is that relevant? Is this just a dumb bug?</p>
  
Tags: <wordpress><cron><cron-job><scheduled-job>
Title: Error Message "Cron not running", but it's working perfectly. CiviCRM 5.43.0
ThreadText: # Error Message "Cron not running", but it's working perfectly. CiviCRM 5.43.0
  
  (Asked by: username_0 on 2021-12-05)
  
  I've seen a couple of Drupal workarounds for this, but not for Wordpress.
  
  The CiviCRM status is below; note that the last reported cron run was manually executed by me.
  
  > All extensions are up-to-date:
  > CKEditor4: Version 5.43.0
  > Contribution cancel actions: Version 5.43.0
  > Event Cart: Version 5.43.0
  > Financial ACLs: Version 5.43.0
  > Theme: Greenwich: Version 5.43.0
  > Custom search framework: Version 5.43.0
  > reCAPTCHA: Version 5.43.0
  > Sequential credit notes: Version 5.43.0
  
  > PHP Up-to-Date
  > This system uses PHP version 7.4.26 which meets or exceeds the recommendation of 7.3.
  
  > Cron Not Running
  > Last cron run at November 26th, 2021 2:35 PM.
  
  I have a separate Cron task for each Scheduled Job, specified on cPanel using the CLI method (because this works better than wget, and no other method worked for me). I can see all tasks are running as they should [Administer > System Settings > Scheduled Jobs], yet the "Cron Not Running" message still pops-up constantly too. This is really annoying.
  
  Here's an example of one of my cPanel Cron jobs, working as expected at 1AM daily (0 1 \* \* \*)
  
  `/usr/local/bin/ea-php74 /home/ACCOUNT/public_html/wp-content/plugins/civicrm/civicrm/bin/cli.php -s MYDOMAIN -j -u USERNAME -p PASSWORD -e job -a version_check >/dev/null 2>&1`
  
  So what triggers this Cron error message? I have set job=version\_check to run only once a day, yet it suggests more frequently - "CiviCRM Update Check (Always)". How can you "always" run a periodic job? Is that relevant? Is this just a dumb bug?
  
  **Tags:** wordpress, cron, cron-job, scheduled-job
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-12-05. Score: 1
  
  It's hardcoded that it needs to be hourly or more: <https://github.com/civicrm/civicrm-core/blob/69cd824e26fc6e90a88e6cf18d9d011c1c85b94e/CRM/Utils/Check/Component/Env.php#L317>
  
  And I'm pretty sure it's tracking the Job.execute job, not any individual job: <https://github.com/civicrm/civicrm-core/blob/69cd824e26fc6e90a88e6cf18d9d011c1c85b94e/CRM/Core/JobManager.php#L72>
  
  > **Comments:**
  > **username_2**: Yes, I get the same thing on any of my sites where we're not running the cron every hour (or more). A lot of ours are set to like every 3 hours or so, so we always have this error come up. I just told it to hide it or whatever so it wouldn't bug me.  
  > **username_0**: I increased the frequency of version_check to every hour, but the message still appears. Clearly in my situation, only a manual job execution will satisfy the criteria to make this go away (and then only for an hour).  The last thing I want to do is start hacking into core functions when my PHP skills are basic.  
  > **username_1**: Is there a reason you need separate cron jobs instead of running job.execute? I.e. just have one cron job with `-a execute` and enable the jobs at Admin - System Settings - Scheduled Jobs. You could still have individual jobs run separately in addition if you really want.  
  > **username_0**: Aha.  I didn't fully understand the baffling cron documentation.  So the solution appears to be;   1. at Admin - System Settings - Scheduled Jobs, enable only jobs that don't require parameters (e.g. version_check, cleanup) and let job.execute manage their execution  2. trigger jobs that require parameters separately  I didn't realise (until I just tried it) that you can trigger jobs without them being enabled at Admin - System Settings - Scheduled Jobs. That's not mentioned anywhere.  Thanks for your help! Problem solved.  
  > **username_1**: Yes civi cron can be difficult to get going, especially the first time.  
  
  ---
  
  