20 days ago
Description of the issue:
Railway CLI (v4, npm @railway/cli) and the API are rejecting every request with
"You are being ratelimited. Please try again later" - even simple commands like
railway whoami. This started after a burst of CLI activity (~30-45 min of
railway up, railway variables, railway add, etc.) while deploying and
debugging several services in project "perfect-enchantment".
Error message:
"You are being ratelimited. Please try again later" - no other detail, on every
CLI invocation.
What I've tried:
- Upgraded from Trial to Hobby plan
- Generated a brand-new API token
- Retried from two different networks/machines
All produced the identical error, so it doesn't appear to be per-token or per-IP.
What I need:
To redeploy the "playwright-service" service in project "perfect-enchantment"
with an updated local Dockerfile build (a bug fix), via railway up. The service
already has a working prior deployment - I just need to push updated code.
1 Replies
20 days ago
The Hobby plan's API rate limit is 1000 requests per hour, and the limit is per-account, which is why a new token or different network does not help. The window resets on a rolling hourly basis, so the CLI should start working again once enough time has passed since the burst. In the meantime, you can push your updated Dockerfile build by connecting your repo and deploying via GitHub auto-deploys, or by triggering a deploy from the dashboard using the Command Palette and selecting "Deploy Latest Commit".
Status changed to Awaiting User Response Railway • 20 days ago
13 days 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 • 13 days ago