Cron job didn't execute for more than 27 hours.
Solution:
Jump to solution
@Brody the issue has now been fixed, thanks! Out of curiosity, was the issue related to the new cron experience and/or Railway metal beta?
21 Replies
Project ID:
4ddd6588-b389-461c-a9d1-033e0ed06a294ddd6588-b389-461c-a9d1-033e0ed06a29
did your last cron exit cleanly?
I can't seem to see any logs
why is that?
There are no logs when I click on the execution
However, I can see some logs when checking the deployment directly
Also super weird that it sent 5 messages at the same time
please provide a direct link
where can i see no deploy logs?
Any of the recent executions (also, I manually triggered an execution 35 minutes ago)
okay thanks, ill raise this
thanks!
for context, old executions do actually show the logs
Solution
@Brody the issue has now been fixed, thanks! Out of curiosity, was the issue related to the new cron experience and/or Railway metal beta?
that service is on metal?
yeah
interesting, no i think we just wernt picking out the correct time range to show you the logs, thank you very much for reporting this
you are welcome!