No. A cron handler should schedule and enqueue work, not perform long-running processing on the Node event loop. Put the job ID or minimal payload on BullMQ and let a worker process it with retries, backoff, and bounded retention. The cron path still needs a distributed Redis lock in Kubernetes, `try/catch`, and idempotent enqueueing. This keeps schedule execution short, prevents duplicate work across pods, and lets worker capacity scale independently.
Installs into .claude/skills of the current project.
Are you the author of Nestjs Scheduling?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-nestjs-scheduling-176c3c46)
No. A cron handler should schedule and enqueue work, not perform long-running processing on the Node event loop. Put the job ID or minimal payload on BullMQ and let a worker process it with retries, backoff, and bounded retention.
The cron path still needs a distributed Redis lock in Kubernetes, `try/catch`, and idempotent enqueueing. This keeps schedule execution short, prevents duplicate work across pods, and lets worker capacity scale independently.
