"railway bucket create" reports "committed: true", but the bucket is not deployed

I'm encountering an issue with Railway Storage Buckets where the CLI reports that a bucket was successfully created and committed, but the bucket does not actually appear in the environment.

Environment

• Project: "jubilant-gratitude"
• Environment: "production"
• Bucket region: "sin" (Asia Pacific, Singapore)
• OS: Linux

Steps to reproduce

I linked the project and selected the production environment:

railway link

railway environment production

Then attempted to create a bucket:

railway bucket create storage --region sin

The CLI returned:

Bucket region 🇸🇬 Asia Pacific, Singapore

Created bucket embedded-cupboard-3gxN (sin (Asia Pacific, Singapore))

Notice that although I explicitly supplied the name "storage", Railway generated a different name.

Immediately afterward:

railway bucket list

returned:

No buckets found in environment production

I then tried again using JSON output:

railway bucket create storage --region sin --environment production --json

The CLI returned:

{

"committed": true,

"id": "40c73e43-7422-4056-b311-c7ef76e5b7da",

"name": "balanced-glovebox-n5XW",

"region": "sin",

"staged": false

}

So according to the CLI:

• "committed" is "true"
• "staged" is "false"
• a valid bucket ID was returned

However, attempting to access or rename the bucket:

railway bucket -b 40c73e43-7422-4056-b311-c7ef76e5b7da -e production rename --name storage

returns:

Bucket "40c73e43-7422-4056-b311-c7ef76e5b7da" is not deployed in environment "production".

And:

railway bucket list -e production --json

still shows no deployed buckets.

Expected behavior

Running:

railway bucket create storage --region sin --environment production

should create and deploy a bucket named "storage" in the "production" environment.

If the command returns:

"committed": true,

"staged": false

then the bucket should be visible through "railway bucket list" and usable by ID/name.

Actual behavior

The CLI creates a bucket resource and returns an ID, but the bucket does not appear to be attached/deployed to the production environment.

It also ignores the requested bucket name and assigns a generated name such as:

embedded-cupboard-3gxN

balanced-glovebox-n5XW

The resulting bucket ID cannot subsequently be used because Railway reports that the bucket is not deployed in the environment.

This looks like the bucket resource is being created at the project level, while the environment deployment/config patch is either missing or not being applied, despite the CLI reporting "committed: true".

Is this a known issue with the current Railway CLI / Storage Buckets implementation?