a year ago
I've got a project with a cron job that's been running successfully every week for 3 weeks. It's now failing with no code changes/updates and I'm unable to see the execution logs to see what's causing the error. FWIW, running the code locally works as expected.
Thanks in advance for your help!
3 Replies
a year ago
Pasting hte logs here for you - does this help?
Starting Container
npm warn config production Use --omit=dev instead.
> todoist-grcocery-list-update@1.0.0 start
> node index.js
Starting Container
npm warn config production Use --omit=dev instead.
> todoist-grcocery-list-update@1.0.0 start
> node index.js
Status changed to Awaiting User Response Railway • 12 months ago
parmstar
Pasting hte logs here for you - does this help?Starting ContainerMar 03 01:03:22npm warn config production Use --omit=dev instead.Mar 03 01:03:22Mar 03 01:03:22> todoist-grcocery-list-update@1.0.0 startMar 03 01:03:22> node index.jsMar 03 01:03:22Mar 10 02:01:46Starting ContainerMar 10 02:01:52npm warn config production Use --omit=dev instead.Mar 10 02:01:52Mar 10 02:01:52> todoist-grcocery-list-update@1.0.0 startMar 10 02:01:52> node index.jsMar 10 02:01:52
a year ago
Nothing helpful there haha. I literally didn't update anything and after working multiple times it just started erroring out. I'm going to push an update and hope that fixes it, but if it starts breaking again for some reason, it's likely hinting at some issue
Status changed to Awaiting Railway Response Railway • 12 months ago
a year ago
Hey Colson, it looks like this might be up and running again? If so, any hints for future readers on what helped fix the issue?
Status changed to Awaiting User Response Railway • 12 months ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago