a month ago
So I am on the free plan and my trial has expired but i have the 1 $ that we get each month but some how i had to restart the deployment to make it online again
and their are no clear logs / info on what happened or why it was offline
now i dont know if their is a redeploy btn but i just toggle the serverless and deploy the and it works
How can i avoid this / am i missing something ?
3 Replies
a month ago
The Free plan requires every service to run in serverless mode (App Sleeping), and your deploy failed because that setting was off, which is why toggling it back on and redeploying fixed it. To avoid this in the future, keep App Sleeping enabled in each service's deploy settings; it can only be turned off on a paid plan.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
The Free plan requires every service to run in serverless mode (App Sleeping), and your deploy failed because that setting was off, which is why toggling it back on and redeploying fixed it. To avoid this in the future, keep App Sleeping enabled in each service's deploy settings; it can only be turned off on a paid plan.
a month ago
i mean its was in serverless from the start still it failed / wasnt in sleeping it was i guess in offline but i had to do the toggle to fix it that doesnt explain why it was offline in the first place
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
To correct our earlier message, the serverless toggle was the mechanism that triggered a fresh deploy, not necessarily the root cause. On the Free plan, services that stop require a manual redeploy to come back online, and toggling the setting is one way to do that. You can also redeploy from the command palette (Ctrl/Cmd + K, then "Deploy latest commit"). More details here: https://docs.railway.com/reference/pricing/faqs#my-services-were-stopped-what-do-i-do
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved sam-a • about 1 month ago