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
I’m using tokio-cron-scheduler where job metadata and states are persisted in NATS, but the job execution logic seems to remain in memory. After restarting the process, I encountered the error: Error getting 679a9805-f852-43b3-9257-3fbf1c75c6c9 from job code.
Questions:
How can I ensure that jobs not yet executed can be resumed or rescheduled after a restart?
Is there an existing mechanism to persist job execution logic, or do you recommend a pattern for recovery?
It seems that only SimpleJobCode and SimpleNotificationCode are implemented. How can these code parts be restored?
The text was updated successfully, but these errors were encountered:
I’m using tokio-cron-scheduler where job metadata and states are persisted in NATS, but the job execution logic seems to remain in memory. After restarting the process, I encountered the error:
Error getting 679a9805-f852-43b3-9257-3fbf1c75c6c9 from job code.Questions:
How can I ensure that jobs not yet executed can be resumed or rescheduled after a restart?
Is there an existing mechanism to persist job execution logic, or do you recommend a pattern for recovery?
It seems that only
SimpleJobCodeandSimpleNotificationCodeare implemented. How can these code parts be restored?The text was updated successfully, but these errors were encountered: