`immediateStart` doesn't actually start the cron job.
See original GitHub issueWhen immediateStart !== false
, the module will execute task.update(new Date())
source. But the update
function first checks if the time has come to execute the task. However, the time hasn’t come because cron job is schedule to be run, say, at midnight.
The immediateStart
functionality should actually execute the task immediately, not check immediately if the time has come. The current functionality just starts the timer of the cron job. I think this should be documented properly or be changed.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Running a cron job manually and immediately - Server Fault
Here's what I did, and it seems to work in this situation. At least, it shows me an error, whereas running from the...
Read more >linux - CronJob not running - Stack Overflow
My cronjob doesn't run?! ... Run ps ax | grep cron and look for cron. Debian: service cron start or service cron restart....
Read more >Cron job troubleshooting guide - Cronitor
Check that your cron job is running by finding the attempted execution in syslog · Begin by grepping for the command in /var/log/syslog...
Read more >Top Reasons Your Cron Job Isn't Running - Airplane.dev
This article walks through the most common reasons why your cron job may not be working as expected: schedule errors, environmental changes, ...
Read more >how can I make cron run a job right now, for testing/debugging ...
You can force the crontab to run with following command: run-parts /etc/cron.daily.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It should probably be renamed as
immediatelyCheck
and documented accordingly.Thanks for this hint! Anyway
immediateStart
should be renamed as its name is definitely confusing (that’s what brought me here).