9 days ago
My free trial expired and a deployment I'd initiated during that window failed. I upgraded to the Hobby plan and triggered a redeploy. The dashboard shows "Hobby" as my current plan and current usage as $0, but the deployment crash-loops immediately on every container start with:
fatal: Your account or project has exceeded the compute time quota.
Upgrade your plan to increase limits.
This repeats every 1-2 seconds (container starts, hits the error, dies, restarts) - the service never actually comes up. Given the plan shows Hobby and usage shows $0, this looks like a stale quota flag from the trial period that hasn't cleared after the upgrade, rather than a genuine limit being hit.
Could there be a leftover quota restriction from the trial that needs clearing manually, or is there's anything on my end I should also check or change?
Thanks,
4 Replies
Status changed to Awaiting Railway Response Railway • 9 days ago
9 days ago
When going to https://railway.com/dashboard when you click on the dropdown in the top left (showing all your workspaces), do you see multiple workspaces or only one?
dev
When going to https://railway.com/dashboard when you click on the dropdown in the top left (showing all your workspaces), do you see multiple workspaces or only one?
9 days ago
Thanks for the quick response.
Only one.
9 days ago
Thank you for clarifying! That log line is coming from your application itself, not from Railway. What app are you running?
Status changed to Awaiting User Response noahd • 9 days ago
9 days ago
You're right, looks like it's coming from Neon (my Postgres provider), not my application itself - it's their own "compute time quota exceeded" message surfacing through the DB connection on startup. Not a Railway issue after all, I'll follow up with Neon directly. Appreciate you looking into it.
Status changed to Awaiting Railway Response Railway • 9 days ago
Status changed to Solved benz1nz • 9 days ago