Cron job did not execute on schedule / has been skipped
Project ID: 4ddd6588-b389-461c-a9d1-033e0ed06a29
21 Replies
Project ID:
4ddd6588-b389-461c-a9d1-033e0ed06a29uh oh, more issues 😦 cron has not been nice to you
Yeah, unfortunately
link to specific service?
last run 11 hours ago eh?
It should technically run every 8 hours
So, there is something fishy about the execution at 10 am. Allow me to elaborate a bit.
The last execution, which is the one at 10 am, somehow does not have any logs when checking the execution itself, specific link for reference https://railway.app/project/4ddd6588-b389-461c-a9d1-033e0ed06a29/service/1c7bdb26-95b7-41cf-a88d-0bd33da12bd9?id=b5607750-d716-454f-a066-8ab85dc9fe44&start=2024-09-25T08%3A00%3A46.955Z&end=2024-09-25T08%3A00%3A55.070Z
hmm yeah odd, the most recent run does not have logs, but the second most recent does, and both ran for nearly the same amount of time
However, when checking the logs from the deployments, the execution at 10 am actually has the application log, but misses the "Starting Container" and "container event container died" messages. https://railway.app/project/4ddd6588-b389-461c-a9d1-033e0ed06a29/service/1c7bdb26-95b7-41cf-a88d-0bd33da12bd9?id=b5607750-d716-454f-a066-8ab85dc9fe44
something is indeed fishy here, ill raise this too, and ive also you some credits for the inconvenience here
Thank you! Also, before I forget to mention it like the last time, this service is using the new cron experience and Railway metal beta.
gotcha, so to sum this up.
the job did run, and on time, but the ui does not reflect that, additionally, you are not able to view the logs on the last listed execution
does that sound correct?
Correct, one thing to add is that the next execution (and potentially more) after this weird behavior did not run. The cron job should be executed every 8 hours and the last execution (the one that is odd) happened 11 hours ago, meaning another one should have run about 3 hours ago.
alright, sorry the the delay here but i have reported it
No worries! I have also confirmed that follow-up executions after the weird execution won't get executed.
interesting
Cron jobs are running again, thanks for fixing it!
haha i'm not directly aware of anything that we did to fix this just yet
:mildpanic: