You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
The node-cron package has a bug that has been going for 6 years: kelektiv/node-cron#232
As a consequence of this bug, some scheduled task stop running without any error message, and thus is incredibly hard to debug
We experienced multiple times at our company in production, forcing us to restart the backend, but this is not an ideal workaround.
Just like for the websockets, it would be nice to have multiple adapters that you pick at the start of the program, e.g.: app.useSchedulingAdapter(new NodeCronAdapter(app));
What is the motivation / use case for changing the behavior?
In production, some scheduled functions will stop running without any error message or log. It produces unpredictible errors, and as a result, the nestjs scheduling functionality is not usable in production.
The text was updated successfully, but these errors were encountered:
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
The node-cron package has a bug that has been going for 6 years: kelektiv/node-cron#232
As a consequence of this bug, some scheduled task stop running without any error message, and thus is incredibly hard to debug
We experienced multiple times at our company in production, forcing us to restart the backend, but this is not an ideal workaround.
Describe the solution you'd like
I would like to have an implementation of different schedulers like https://github.com/node-schedule/node-schedule#readme or others, to provide an alternative to node-cron.
Teachability, documentation, adoption, migration strategy
Just like for the websockets, it would be nice to have multiple adapters that you pick at the start of the program, e.g.:
app.useSchedulingAdapter(new NodeCronAdapter(app));
What is the motivation / use case for changing the behavior?
In production, some scheduled functions will stop running without any error message or log. It produces unpredictible errors, and as a result, the nestjs scheduling functionality is not usable in production.
The text was updated successfully, but these errors were encountered: