2 days ago
I am on a free account and I have 1 Laravel application with a MySql db backend.
On my Projects page it says:
Out of Credits | You have run out of credits. Your balance will reset in 20 days.
But I have $0.98 left of my free credits according to the informationn box at the top right on the Projects page.
In the status for this application both services say that they are paused from exceeding limits. But I don't believe any limits have been exceeded for this application?
So is there an issue where the system now thinks that some limits have been exceeded when they haven't or that I have run out of credits when I still have some credits left?
4 Replies
2 days ago
Your services were originally stopped back in late March when your trial ended and the workspace moved to the Free plan. The "Out of Credits" message refers to that original event, not your current billing cycle. Your current cycle usage is only about $0.02 against the $1 monthly credit, so you do have credit available. Because the services have been stopped for more than 30 days, they will not auto-redeploy. You will need to manually redeploy each service from the removed deployment's 3-dot menu, and make sure App Sleeping is enabled on each service under Settings, since the Free plan requires it.
Status changed to Awaiting User Response Railway • 1 day ago
2 days ago
I don't see how the services can have been stopped for more than 30 days since the application has been used multiple times in the last 7 days?
Looking at the Activity status both the services were Deployed and subsequently put back to sleep only 8 hours ago.
When I go to the Deployments page for each of the services it says:
Limited Access
Deployments have been removed because you have run out of resources.Upgrade your plan to continue deploying.
But I don't see how these services can have exceeded any resources?
Status changed to Awaiting Railway Response Railway • 1 day ago
2 days ago
Your current cycle usage is only about $0.02 against the $1 monthly Free plan credit, so you are correct that you should have credit remaining. The "Limited Access" restriction you are seeing is a Free-tier resource limitation that temporarily removes deployments during high-demand periods. Once the restriction lifts, you will need to redeploy each service manually from the 3-dot menu on the most recent deployment, since removed deployments do not resume automatically.
Status changed to Awaiting User Response Railway • 1 day ago
2 days ago
I am not sure that this is the reason my application can't be used? The message on the Deployments pages specifically states that I have run out of resources: Limited Access
Deployments have been removed because you have run out of resources.Upgrade your plan to continue deploying.
If I understand the Free tier peak hours restriction section of the document you have linked to, which is the section I assume you are referring to, I don't see how this applies to my situation?
There has been no changes to the application that needs a new deployment from source code. I only noticed this issue because I was trying to access the application as a user and got an error page instead of the application page.
So there have not been any new deployments scheduled for the application itself. I assume that these deployments are just the wake up from sleep deployments that happen as the services are configured to go to sleep when not used for a specified time.
So are you sure that the issue I am seeing is an issue that because the Railway servers are under heavy load, they have completely removed all the deployments for my application as I am on the free tier and I will manually have to instigate new deployments for both the application service and the database service to get the application back up and running again? If that is the case, how will I know when the servers have capacity for free accounts applications again? And how can I ensure that any data entered into the database by users using the application up until now is kept after the deployment?
Status changed to Awaiting Railway Response Railway • 1 day ago
2 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 1 day ago