default schedule not honored for cron queue jobs

Created on 18 October 2015, over 9 years ago
Updated 8 January 2025, 3 months ago

Hi

Not sure if this is "by design", but I found this confusing.

I have a mix of regular cron (hook_cron) and cron queue (hook_cron_queue_info) jobs. (In the UC jobs list, the regular ones show a title of "Default Cron Handler" (unless they are core jobs that you changed the name for in ultimate_cron.cron_inc), and the cron queue ones show a title like "Queue: {queue name}").

All jobs use the Default (Crontab) scheduler, and I'm using poorman's cron, interval 1 minute (I turned off my wget cron generator).

The default rule for the Crontab scheduler is * */6+@ * * * (as configured at admin/config/system/cron/scheduler/crontab)

When I edit a non-overridden regular cron job, such as Feeds Cron (at admin/config/system/cron/jobs/list/feeds_cron/edit), I see on the right side of the edit form, in the Crontab frameset, under the rules box, it says: Semi-colon separated list of crontab rules. (Blank = * */6+@ * * *).

When I edit a non-overridden cron queue job, such as Queue: feeds_push_unsubscribe, the text in the editor window says: Semi-colon separated list of crontab rules. (Blank = * * * * *).

I am able to override the rule for the cron queue job (to something like */10+@ * * * *) and get the queue to be processed every 10 minutes instead of every one minute.

So my question is, why is the crontab default rules schedule not being used for cron queue jobs? Only for regular cron jobs?

This can be similarly be seen in the UC jobs tab in the Scheduled column. It jumps between * * * * * and * */6+@ * * * depending on the nature of the cron job.

Is this a bug? Or serving some purpose?

Thanks for your info

πŸ› Bug report
Status

Closed: outdated

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States hanksterr7

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡°Denmark arnested

    I'm closing this since Drupal 7 is now unsupported and there will be no more development on the Drupal 7 branch of Ultimate Cron either.

    Thank you for taking the time and effort in reporting this issue, even though it never got resolved.

Production build 0.71.5 2024