CFFM Development only.

Railway Settings reports:

"Invalid region us-west2 is configured on this service and is blocking deployments."

Public-safe context:

Project: CFFM

Environment: development

Service: cffm-development-api

Volume: cffm-development-data

The service and its attached persistent volume both display US West

(California, USA).

Railway documentation currently lists US West Metal / California with the

region identifier:

us-west2

The persistent volume is connected to the service at:

/persistent-data

The repository configuration:

deploy/cffm-dev/railway.json

contains no region, replicas, or multiRegionConfig setting.

No staged region change was observed.

We have not requested or performed:

• a service region migration
• a volume migration
• a volume recreation
• a deployment as a test

Please inspect the underlying service/workspace control-plane configuration

for stale or malformed region state.

Could you confirm whether the existing service can be safely normalized to

the currently valid US West Metal identifier us-west2 without recreating or

migrating cffm-development-data, while preserving the existing

/persistent-data attachment and its data?

This is Development infrastructure only.

No secrets, environment-variable values, private media, training data, or

resource UUIDs are included in this public post.

If specific Project, Environment, Service, or Volume IDs are required, please

request them through a Railway-approved private channel.

Please do not migrate the service or volume to another region without our

explicit approval.