Cron Doctor
Free cron job checker. Find configuration risks before monitoring completion.
Check cron syntax, timezone context, and supported reliability settings across Unix cron, GitHub Actions, Kubernetes, systemd, and Laravel. No signup needed. Static analysis does not execute your job or prove it succeeded.
Check a job for free · Running 21–50 jobs? See Pro at $9.99/month for one owner.
See supported schedule details and configuration risks with source evidence. Upcoming times appear only when the supplied context supports them; a report does not prove runtime success.
One owner. 21–50 jobs. $9.99/month.
Keep your scheduler. PingCron Pro covers up to 50 monitors across cron, GitHub Actions, Kubernetes, systemd, and Laravel workloads, with email, Slack, Discord, and webhook alerts. It watches for expected check-ins after your work completes; it does not execute, repair, or retry that work.
For 30 monitored jobs and one user, monthly list prices are PingCron Pro $9.99, Healthchecks Business $20, and Cronitor Business $65. Healthchecks offers 20 free checks and shared projects. Cronitor Business includes 12-month retention and SMS/on-call features. Choose PingCron for its price at this workload count when these monitoring features fit.
USD monthly rates checked October 17, 2026; taxes, discounts, and add-ons excluded. Compare the tradeoffs: Healthchecks · Cronitor.
Pro retains 30 days of data for daily reported-outcome summaries. The individual list shows the latest 100 receipts, not a searchable month of application logs. Shared account access starts on Team.
The checker is free. Monitoring Free includes 5 monitors and 7-day history, with no credit card. Pro signup continues to checkout.
Turn a report into one verified monitor
- Analyze one intended job with its scheduler and timezone context. A partial report leaves unsupported behavior unknown. Analysis does not create a monitor or prove that your output is correct.
- Use Protect this job in a supported report. Review the owning account, schedule, timezone, and grace period before creating a monitor. The diagnosis stays in this tab through sign-in; closing or reloading the tab clears an unsaved diagnosis. Some configurations cannot be represented as a monitor expectation.
- Install the check-in only after required work and output checks succeed. Include normal runtime and scheduler delay in the grace period. A missing signal can reflect job, scheduler, host, or reporting trouble; detection and alert delivery take additional time.
- Confirm a real completion receipt and verify your alert destination. Test missed-run and recovery behavior on an isolated monitor before adding the rest.