5 months ago
I have a serverless selenium container that has been woken by a cron job reliably for a few months.
It would not wake and i had to manually restart the container.
Is this a known issue on Railway? Any way this can be prevented?
1 Replies
5 months ago
https://docs.railway.com/deployments/serverless#caveats
Slept services still consume a slot on Railway's infrastructure, enabling Serverless de-prioritizes your workload and in remote cases, may require a rebuild to re-live the service.
Status changed to Awaiting User Response Railway • 5 months ago
4 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 • 4 months ago