Fixed
Project:
Drupal Worker
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2026 at 20:24 UTC
Updated:
11 Nov 2026 at 20:55 UTC
Jump to comment: Most recent
A job runs only when its schedule says. Work often arrives at a moment the site knows about (a webhook stored an event, an invitation was sent, a queue got its first item), and then waits for the job's next turn. Making that wait short means running the job every few seconds, which is a process and a full Drupal bootstrap each time, mostly finding nothing to do. The worker only hears from the site at its refresh (one minute at the least), so the site has no cheap way to say "now".
druker.wake service (Wake::wake($job), a job or its id) and drush druker:wake <id|name>. A signal is an empty file named after the job's id, in a wake directory.$settings['druker_wake_dir']: a path or stream URI, or FALSE to switch waking off. By default it is private://druker/wake when the site has a private file system, and otherwise a directory of the site's own under temporary://. The schedule tells the worker where it is, as a new top-level wake_dir in drush druker:jobs.drush druker:check says when waking is off or the directory cannot be written.wake_dir in JobManager::getJobsForServer(), the worker's Schedule struct, and examples/sample-output.json. An older worker ignores it, and a newer worker against an older site does not wake.worker/wake_test.go, an end-to-end supervise test, Kernel WakeTest, and JobManagerTest.Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
valic