Cron not working?

[sdenike]

So I have a random issue I am seeing from time to time, I was hoping it was from a single service, but it looks like it could be from multiple. Originally, I thought the shared calendar from the Gamechanger app was broken as updates to the subscription calendar within the app never seemed to make it through to Calunite, unless I would edit the config file (Even just adding white space, deleting it, and closing the file. This would trigger calunite to update), or by restarting the Docker container.

I have the cron set to run every 15 minutes, which I feel it might but not for all remote subscriptions. I recently noticed this happen with the calendar in another sports app called Sprocket Sports. If I do the whole edit, exit of the config or restart the container it pulls the updates fine.

Here is a snippet of the log of when I last noticed things not aligning, and you can see where I did the edit to fire it off

2026/01/21 15:36:02 /config/config.yml read successfully
2026/01/21 15:36:02 YAML parsing done
2026/01/21 15:36:09 Initial merge finished
2026/01/21 15:36:09 Started merge cronjob
2026/02/01 17:02:30 Modified /config/.config.yml.swp - scheduling reload...
2026/02/01 17:02:30 /config/config.yml read successfully
2026/02/01 17:02:30 YAML parsing done
2026/02/01 17:02:30 Stopped previous cronjob

Very possible I am doing something wrong with the container, but I thought I would bring this up in case it is a strange bug.

[Jojodicus]

Cannot reproduce on my side, works and updates perfectly. If you use a non-default interval, have you checked if your syntax for the cronjob is correct? Note the quotes and the @ symbol, you will also need quotes if you use a more "typical" cron expression.

You don't need to specify settings where you'd want to use the default though.

Calunite swallows errors regarding cron formatting, that is definitely a bug. But I'm not really sure if anything more is going on here.

[sdenike]

I had specified the CRON using the default every 15m per the documentation, I have since commented that line out of my docker-compose and keeping an eye on it.

[Jojodicus]

whoops, commit auto-closed the issue, wasn't my intention

I also tried reproducing it again, seems to work as expected. Maybe there was a typo or something else, so together with the ignored error it would lead to it silently failing.

[sdenike]

Seems that removing the CRON in the docker-compose and letting the default just be default, it is working. Not sure why specifying it on my setup was causing it to not run.