Storage Bucket create rejected by backend although plan/config validation succeeds

I’m troubleshooting a Railway Storage Bucket creation failure in a production environment.

The failure is isolated to the bucket CREATE operation itself.

Command shape:

railway bucket create <new-display-name> --region sin --environment production --json

The command returned non-zero and no bucket was created.

Unfortunately, the original wrapper discarded stderr/stdout from that terminal execution, so the exact backend rejection message is no longer recoverable.

I have since added sanitized subprocess diagnostics, but I do not want to consume another production create attempt until the original failure is understood.

Current investigation results:

• Railway CLI 5.49.2 was used for the failed execution.
• I independently tested CLI 5.62.1.
• The bucket create implementation is unchanged for the relevant behavior.
• The CLI command/argument contract is valid.
• Project and production environment linking succeeds.
• Bucket list/info succeeds.
• Existing source bucket is healthy.
• Region sin is accepted.
• The proposed 53-character display-name shape is accepted by a read-only Railway config plan.
• Workspace plan: Hobby.
• Trial/account state is active.
• Bucket count: 1 of the project limit of 3 exposed by the current plan contract.
• Storage usage is approximately 112 KB.
• No usage-limit, workspace restriction, or bucket quota issue is surfaced.
• Workspace role is Admin.
• Environment patch history contains no failed or stale bucket-create patch.
• Current pending patch count is zero.
• A read-only config plan accepts exactly one new bucket resource with region sin.
• No current Railway storage incident is reported.
• The failed target bucket does not exist.
• No orphan successor bucket exists.

The failed execution was fail-closed before any copy, credential retrieval, environment reference update, or deployment.

Could a Railway team member inspect backend/provider logs for the failed bucket-create mutation and determine why the create request was rejected?

IDs are available to Railway staff on request through whatever safe channel you recommend.

I am specifically trying to determine whether the rejection was caused by:

• mutation-level authorization,
• backend provisioning,
• an internal storage service error,
• or another provider-side condition not exposed by the CLI/API.

I do not need application-level debugging; I only need the Railway Storage Bucket create rejection diagnosed.