7 months ago
Did something change with Cron just recently? I've been using ^4.0.5 for days and everything has been working fine until today.
Now the bot is crashing on deploy/restart with the message in the image.
So I thought it might be something to do with ICU, so I removed reference to the America/Chicago Timezone, but that didn't fix it.
TL;DR
I've already removed all timezone options, which was the first fix.
But maybe node-cron@4.x is still trying to use ICU internally for future scheduling predictions?
So should I downgrade to v3.0.2 which might not look for ICU?
6 Replies
Ok, apparently was just Railway having a moment. Everything is working ok now.
🤷♂️
7 months ago
Yeah its being Resolved now ig.
7 months ago
This is an issue with your application or configuration, the Railway platform has no involvement in your code's time value.
I've gone ahead and bountied this thread so that the community can help you with this issue.
