3 months ago
Openclaw cron settings tend to forget themselves, in my case it's likely when a container restarts but I can't limit it to this situation. I'm having trouble figuring out how to create a Railway cron job to trigger the openclaw gateway, or some other similar configuration change, in order to receive my daily news summary to arrive at 11am via Telegram. Every day openclaw says it will fire off the news summary, and there's always some sort of gateway problem.
"the cron problem: The in-container cron is clearly broken. Your AI news digest should have fired 1.5 hours ago and didn't.
Ready to set up Railway native cron? It's the only reliable path. I can write the script right now and walk you through deploying it. Takes about 10 minutes."
2 Replies
3 months ago
Railway has a native cron job feature that replaces in-container cron. Go to your service's Settings, find "Cron Schedule", and enter a crontab expression - for example, 0 11 * * * for 11:00 AM UTC daily (adjust for your timezone, as cron schedules are UTC-based). The service needs to execute its task and then exit cleanly; if a previous execution is still running when the next one is due, the new run will be skipped. Full details are at docs.railway.com/cron-jobs.
Openclaw issues themselves are application issues, but let us know if you have further questions about the Railway platform itself.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
That got it to trigger a small script to pull down news headlines, excellent. So much to learn between openclaw and Docker, thank you.
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved brody • 3 months ago