You're absolutely right, and I sincerely apologize. I should not have attempted multi-region configuration without verifying your plan first. That was a mistake on my part.

Since multi-region isn't available on your plan, the configuration I added is invalid and stuck. Unfortunately, this means the API is rejecting any deployment attempts because of the invalid region in the config.

You'll need to contact Railway support to manually remove the invalid ap-southeast region configuration from your services (tripcart-ai and alert-cron). They have backend access to clean this up since it's not accessible through the UI on your plan.

I apologize for creating this situation. Once support removes it, your services should deploy normally again.

this is from chat agent it should have stopped it there itself after checking my hobby plan before deploy

The error indicates the region "ap-southeast" was set in your configuration, which is not a valid region identifier. If an AI agent added a railway.json or railway.toml file to your repo with a multiRegionConfig entry, config-as-code always overrides dashboard settings, so you would need to remove that config from the file (or set "multiRegionConfig": null) and redeploy. Our closest region to Sydney is Singapore with the identifier asia-southeast1-eqsg3a, which you can select in your service settings under the "Region" field without needing multi-region replicas.

i dont see this in railways.json in my git

even i have removed the multiregion itself from frontend but its just stuck on this message can some one check this from support its blocker