Cron job didn't execute for more than 27 hours.

2 years ago

(no markdown available for this content)

21 Replies

2 years ago

4ddd6588-b389-461c-a9d1-033e0ed06a29


2 years ago

did your last cron exit cleanly?


2 years ago

I can't seem to see any logs


2 years ago

why is that?


2 years ago

There are no logs when I click on the execution

1287855684813193360


2 years ago

However, I can see some logs when checking the deployment directly

1287855809052672120


2 years ago

Also super weird that it sent 5 messages at the same time


2 years ago

please provide a direct link



2 years ago

where can i see no deploy logs?


2 years ago

Any of the recent executions (also, I manually triggered an execution 35 minutes ago)

1287859767229943859



2 years ago

okay thanks, ill raise this


2 years ago

thanks!


2 years ago

for context, old executions do actually show the logs


2 years ago

1287860436867481730


2 years ago

@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?

1288186065579933756

1288186065844310070


2 years ago

that service is on metal?


2 years ago

yeah


2 years ago

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


2 years ago

you are welcome!


Welcome!

Sign in to your Railway account to join the conversation.

Loading...