2 months ago
Hi Railway team,
I have a Cron service called "historical-initial-scraper" in my project "veStocks-Scraper". My Python script had a bug where the process never exited, so a cron execution started at 12:49 PM (March 20) got stuck running for over 1 hour.
To fix the issue, I removed the active deployment, which killed the container. I then deployed a corrected version of the code that now exits properly (confirmed by a new execution that completed in 42 seconds with a green status).
However, in the "Recent Executions" list (Cron Runs tab), the old 12:49 PM execution still shows a "Running..." label, even though the container was already removed. The Metrics tab confirms 0 CPU and 0 memory usage, so the process clearly no longer exists. But the stale label is confusing.
Is it possible to clear or remove that old stuck execution record so it no longer shows as "Running"?
Thank you.
Attachments
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
This is a known UI issue where a cron execution's status is not updated when the underlying deployment is removed while it's still running. There is currently no way to manually clear that stale "Running" label, but it does not affect your future cron runs or billing. Your newer execution completing successfully in 42 seconds confirms everything is working correctly now.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago