What should I log for cron jobs?
Log the job name, start time, end time, duration, result (success or failure), error message and stack trace. Use Winston with JSON format and write to both console and a file (logs/cron.log). Include enough context to debug failures without re-running the job.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Cron Job Error Handling and Monitoring Reliable Scheduled Tasks in Node.js
Always wrap the job logic in try-catch. Log the error with details (message, stack, job name). Send an alert (email, Slack, SMS) to the admin. Track the failure in a CronJob database collection. Consider retrying with exponential backoff for transient errors.
Use a flag: if (isRunning[jobName]) { console.log('Already running, skipping'); return; } Set isRunning[jobName] = true before the job and false in a finally block. This prevents multiple instances from running simultaneously if the job takes longer than the interval.
Track each job execution in a CronJob database collection (jobName, status, startTime, endTime, duration, result, error). Create a /health/cron endpoint that shows the last status and failure count for each job. Set up alerts for failed jobs and long-running jobs.
Still have questions?
Browse all our FAQs or reach out to our support team