NestJS @Cron jobs stop firing when app runs as Windows service

dhil rohith — Tue, 26 Aug 2025 07:57:33 +0000

I have a NestJS application running on a Windows Server, where the app is installed as a Windows Service (via nssm).

Inside the app I use @nestjs/schedule with 5 cron jobs:

one runs every 1 minute

one runs every 5 minutes

others run every 10 min, 15 min, 1 hour, etc.

The issue: the 1-minute and 5-minute jobs stop firing after some time, but the rest continue normally. The service itself remains running, and there are no error logs.

Example code for the 5-minute job:

import { Cron } from '@nestjs/schedule';
import { Injectable, Logger } from '@nestjs/common';

@Injectable()
export class TasksService {
private readonly logger = new Logger(TasksService.name);

@cron('*/5 * * * *')
async scheduledHandleCronOld() {
this.logger.log('Old File Processing Job >> Starting scheduled handleCronOld...');
try {
if (this.config.get('SFTP_FILE_FORMAT') === 'OLD') {
await this.handleCronOld(null);
} else {
this.logger.log('Old File Processing Job >> Ended due to config is NEW File Format...');
}
} catch (error) {
this.logger.error(Old File Processing Job >> Scheduler error: ${error.message});
}
}
}

NestJS cron scheduler stops running silently when app is hosted as Windows Service

dhil rohith — Tue, 26 Aug 2025 07:13:12 +0000

Hey everyone,

I’m running a NestJS application as a Windows service on a Windows server.
Inside this service (named sftp), I have 5 cron schedulers configured. Each runs at different intervals (e.g., every 1 minute, every 5 minutes, etc.).

The issue I’m facing:

The 1-minute scheduler and 5-minute scheduler stop running unexpectedly.

The service itself is still up and running, and the other schedulers continue working fine.

From the logs, I can see that the job starts and completes normally (including successful disconnect).

Normally, the scheduler should fire again in the next cycle, but it never does.

No errors are logged, no suspicious behavior before it stops, and processing time is normal.

I already have error handling in place, so it doesn’t look like it’s silently failing.

Has anyone else experienced a scheduler just stopping without errors while the rest of the app continues?
Any ideas on what could cause this or how to debug further would be really helpful.

Logs (just before it stopped running):

[2025-08-20 14:30:00] [SftpOldService] INFO: Old File Processing Job >> Starting scheduled handleCronOld... | Host: SN2EBYX1C0032, PID: 24325
[2025-08-20 14:30:00] [SftpOldService] INFO: Old File Processing Job >> Started | Host: SN2EBYX1C0032, PID: 20456
[2025-08-20 14:30:00] [SftpOldService] INFO: Old File Processing Job >> Started with config:
Host: 123.227.7.73
Port: 22
Username: xxxyyy
Path: /mh | Host: SN2EBYX1C0032, PID: 24325

[2025-08-20 14:30:00] [SftpOldService] INFO: SFTP Connected successfully to 123.227.7.73 | Host: SN2EBYX1C0032, PID: 24325
[2025-08-20 14:30:00] [SftpOldService] INFO: Old File Processing Job >> SFTP CONNECTED | Host: SN2EBYX1C0032, PID: 24325
[2025-08-20 14:30:00] [SftpOldService] DEBUG: Old File Processing Job >> Files in directory /mh: | Host: SN2EBYX1C0032, PID: 24325
[2025-08-20 14:30:00] [SftpOldService] INFO: Old File Processing Job >> No CSV files found in SFTP directory | Host: SN2EBYX1C0032, PID: 24325
[2025-08-20 14:30:00] [SftpOldService] INFO: SFTP disconnected successfully | Host:SN2EBYX1C0032, PID:24325

DEV Community: dhil rohith

NestJS @Cron jobs stop firing when app runs as Windows service

NestJS cron scheduler stops running silently when app is hosted as Windows Service