a month ago
Issue: Deployment fails with "Free plan deployments must be serverless. Please go to your service settings and turn on the serverless flag." even though Serverless is already enabled.
Steps already tried:
- Confirmed Serverless toggle is ON in Settings > Deploy
- Used command palette (Cmd/Ctrl+K) > "Deploy latest commit" instead of regular Redeploy
- Error still occurs after fresh deployment
Plan: Free plan
Request: Could you manually trigger a fresh deployment on your end, as this appears to be a sync issue between the toggle setting and the live deployment state (seen in similar resolved tickets)?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your latest deployment has completed successfully and your service is running. The earlier failures happened because redeploying an existing deployment reuses the configuration snapshot from when that deployment was originally created, which can carry a stale serverless flag. Using "Deploy latest commit" from the command palette (as you tried) creates a fresh deployment that reads the current toggle state, which is why it ultimately worked. Going forward, when you need to redeploy on the free plan, always use "Deploy latest commit" rather than redeploying an older deployment to avoid this.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago