3 months ago
Cron jobs have been unable to start for over an hour. Message says to contact support if it persists.
https://railway.com/project/e3464d1e-7a9d-4dad-ae70-08e9b454f87f
Any idea what's going on?
8 Replies
3 months ago
!t
3 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response uxuz • 3 months ago
To the extent it is useful, here's the contents of railway.daily.toml, which configures the Cron job:
[build]
builder = "DOCKERFILE"
dockerfilePath = "Dockerfile"
[deploy]
# Cron schedule: Daily at 10:00 AM UTC (2:00 AM PST / 5:00 AM EST)
cronSchedule = "0 10 * * *"
startCommand = "/app/scripts/daily.sh"3 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
A quick update: I duplicated the service and the cron job was able to run. I deleted the old service and everything seemed fine. No idea why this is the case. But I say so in case it's useful to anyone else.
3 months ago
We just fixed an issue related to CRONs defined in config-as-code. If you see another drift, a redeploy or hitting "run now" should fix
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved itsrems • 3 months ago
3 months ago
🛠️ The ticket Scheduled Tasks Issue has been marked as backlog.
3 months ago
✅ The ticket Scheduled Tasks Issue has been marked as completed.
