5 days ago
When a CRON fails, it currently says "Deployment Failed". But this is not correct - the deployment worked, but the job itself failed.
Deployment failed to me kinda implies a railway issue. If I see 'Deployment Failed' for other services, it would be a significant issue. But part of the reason we are running CRONS in the first place is because we are trying to interact with sometimes-flakey external APIs.
I'm filing this ticket because I was actually reached out to by a Railway rep who was trying to understand why my deployments were failing so much. Hopefully this shows that this issue is causing operational overhead for y'all as well as for me.
As I've mentioned on Discord (down right now so I can't link the thread), the CRON system in general feels a bit under-baked. If there is another pattern for periodically running jobs that is more suitable for Railway, I would be curious to hear suggestions.
P.S. Case in point - I can't link my CRON jobs as the affected service in this dropdown, so linking a different service.
0 Threads mention this feature
3 Replies
Status changed to Awaiting Railway Response Railway • 5 days ago
5 days ago
Hey! Thank you for the feedback. Can you clarify where you see "deployment failed" for a cron service? On the canvas, it should say "last run failed" or something to that effect.
Status changed to Awaiting User Response Railway • 5 days ago
5 days ago
Status changed to Awaiting Railway Response Railway • 5 days ago
5 days ago
Thanks for the screenshots - you're right that the email notification says "Deploy Crashed" which is misleading for cron jobs whose task exited non-zero. The canvas correctly shows "Last run failed" but the email doesn't make that distinction.
I'm going to convert this to a feedback thread for us to keep track.
Status changed to Awaiting User Response Railway • 5 days ago