Cron manager nil pointer exception

Questions / Help
1

Hi,

We’re on Fly Cron Manager for scheduled Machines, which is still the documented blueprint-style setup. The monitor process keeps crashing in a tight loop: nil pointer in evaluateJob / findEvent, process restarts every few seconds. It’s the same failure mode as fly-apps/cron-manager#18 (open since 2024). There’s a concrete proposed fix in #24 (guard nil machine / don’t fall through on failed MachineGet); that’s also still open, so we’re not sitting on a mystery regression on our side.

Schedules still run; the problem is operational. Those panics and restarts flood our observability stack and read like a production incident even though the cron work itself is going through. We need a clear line from Fly: is Cron Manager still a supported path, will a fix land in main and a published image (and roughly when), or should we treat this as deprecated and replan? If there’s an interim workaround (pinning, config, alternative product), we’ll take it.

Thank you!

2

Hi Matyas,

cron-manager is generally unmaintained beyond keeping it up to date with security patches. I’ll try to have a look at that patch you pointed to but can’t promise any ETA so if you have a pressing need you could either look elsewhere, or fork cron-manager, apply the patch if it suits yuor needs, and use the included Dockerfile to build a custom image.

Cheers!