bugs blocking development - need timeline for fixes
Anonymous
HOBBYOP

2 months ago


Project: WebCraft (ID: dfe15b97-7e35-47c8-be30-0772ccb4da6b)

Issues:

1. Cannot modify service configurations
   - Memory limit changes don't apply
   - Custom Start Command changes don't apply
   - Deploy completes but config stays old
   - Status: Stuck for 10+ days

2. Cannot delete stuck services
   - Redis-cache (ID: f09ea62a-378b-4119-ae90-00def84a4f9f) offline 3+ hours
   - Cannot delete via UI or CLI
   - Blocking all development

3. Default project memory allocation too high
   - New projects default to 8/8 vCPU and Memory
   - Cannot reduce to 2/4 or lower
   - Makes it impossible to add new services
   - Should be configurable or lower default

Questions:
- When will these bugs be fixed?
- Can you provide a timeline?
- Is there a workaround?

This is critical - project is completely blocked.
Solved

1 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


sam-a
EMPLOYEE

2 months ago

The Redis-chache service shows as successfully removed in our system, so that deletion did complete. For configuration changes like memory limits and custom start commands, note that all changes are collected as staged changes and must be explicitly deployed by clicking the "Deploy" button in the staged changes banner on the canvas. Regarding resource limits, the Hobby plan allows services to vertically autoscale up to the plan maximums, but services only consume what they actually need. You can constrain individual services by setting Replica Limits under service Settings > Deploy > Replica Limits to cap the vCPU and memory each service can use.

Let us know if you need more help.


Status changed to Awaiting User Response Railway 2 months ago


Railway
BOT

2 months 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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...