Hi Railway Team,

I need help with a persistent volume attachment on an isolated development service.

Project: PeopleFlow Cloud DEV

Project ID: 85150549-5ec2-47d5-b7cf-16ba0e57fc70

Service: peopleflow-dev

Service ID: febbc7e8-fce0-4c4c-b575-f2297f1d1e69

Environment ID: 4d4c28e2-7532-40bf-8946-6ceadf604d18

The service is healthy and currently has:

multiRegionConfig: {sfo: {numReplicas: 1}}

I am trying to attach one 512 MB persistent volume mounted at:

/app/data

The volume is successfully staged and the staged changes are committed, but afterward the volume disappears and does not appear in the environment or service configuration.

This has happened repeatedly with these volume IDs:

f6755df0-b33b-400e-aeaa-4fbf85f2d4af

815fb1c9-1a78-498a-96ba-4314788e5abc

802dbaba-5159-4fc6-90c0-0ca6f0db9ea9

Latest commit workflow:

0e1ac4d7-ab25-4100-bda3-6ed8f54bf560

Railway documentation states that replicas cannot be used with volumes, but it is unclear whether an explicit numReplicas: 1 counts as replica mode.

Could you please confirm the exact configuration change required to make this service volume-compatible while keeping exactly one running instance?

Specifically, should we:

remove multiRegionConfig completely,

set multiRegionConfig to null,

or use another configuration?

Please also advise why the volume commit completes without exposing an error even though the volume does not become attached.

Thank you.