cron expression error and cron job not working as expected.
See original GitHub issueAccording to the docs
First thing is the cron expression link that you’ve mentioned in the docs results in error with “Unexpected end of expression.”
I used the same cron expression in the code:
And cron runs every second :
Here’s the code for queue, worker and required things :
node version : v11.14.0
"bullmq": "^1.9.0",
Redis:
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Cron job troubleshooting guide - Cronitor
The common reasons cron jobs fail · Schedule errors are easy to make. Cron job schedule expressions are quirky and difficult to write....
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 >Why is my crontab not working, and how can I troubleshoot it?
The vast majority of "my cron script doesn't work" problems are caused by this restrictive path. If your command is in a different...
Read more >linux - CronJob not running - Stack Overflow
WTF?! My cronjob doesn't run?! Here's a checklist guide to debug not running cronjobs: Is the Cron daemon running? Run ps ax |...
Read more >Why crontab scripts are not working? - Ask Ubuntu
cron ignores PATH from that file, so runnning somecommand from your script will fail when run with cron, but work when run in...
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 FreeTop 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
Top GitHub Comments
Oh, wow! It’s pretty bad to have that link in the docs. That should definitely be changed.
@5achinJani, “15 3 * * *” is definitely a valid cron expression: See also: https://en.wikipedia.org/wiki/Cron
It look like the tool you’re using is trying to evaluate the expression using as a “Quartz cron” expression, which is a non-standard format. (In my opinion, it’s deeply irresponsible of Quartz to use the word “cron” when their formats are not interoperable.)