I’m running a CF11 box and recently it’s just stopped running scheduled tasks. There’s nothing in the logs to say they’ve failed or misfired and when I pause it and resume it, it updates the “next run” time, but that just comes and goes. Running it once in the admin doesn’t work, however going to the URL that it’s meant to be hitting works just fine

As of end of last week we've noticed this ACF2021 running on AWS with CommandBox. Has been stable. Redeploy fixes it for a short while.

Yes a restart fixes it for me for a little while

Friday was when we noticed it first but may have stopped prior to that as it silently fails

Yes that’s the most frustrating part. Interestingly it seems to be Fridays it fails for us too

Linux and clustered here. Is still quartz though under the hood

I did find a workaround of using windows scheduled tasks to hit the url with the cmd shell but it’s not really an ideal solution

We spin up scheduled tasks programatically (send emails etc) so is a big deal for us as not used for polling

I don’t blame you. We experimented before with SQS as a replacement

ha nice! We have them in database but it is very slow to query and we can't upgrade to 2023 as it's a different schema (I think that was it - there was a reason we couldn't upgrade anyway)

Yeah this box is due to be upgraded to 2023, the staging server is currently being tested just now so I’m hoping the problem will go away but in the meantime it’s annoying

Its cleaner and easier to run a corn job / windows task that calls a local script to do what you want, ie curl -e localhost/path/to/something.cfm , OS control, and it does not break when you have 100+ tasks running a day.

If it's just doing dumb polling on a single server then maybe. If you want any kind of ability to pause, chain, cluster, schedule then Quartz does some really powerful stuff

We are working on massive improvements for batching and scheduling. @Charvi you might have a couple interested parties in helping with that here... :)