Hello Railway support,

I am trying to deploy Evolution API (Docker image: atendai/evolution-api:v2.3.5) on a completely new Railway project using the free plan.

Current setup:

- 1 PostgreSQL service

- 1 Redis service

- 1 Evolution API service

- Single replica only

- Single region only

Problem:

The deployment fails before container creation and before compilation starts.

Error messages repeatedly mention:

- multiRegionConfig enabled

- invalid regions like "sfo" and later "iad"

- deployment rejected because free plan only supports single-region deployments

Important:

I already removed all extra regions manually.

I also removed extra replicas.

Currently the service shows:

- only 1 region

- only 1 replica

However Railway still behaves as if multiRegionConfig remains enabled internally.

I created an entirely new project and the exact same issue happened again immediately after deployment.

The deployment never reaches actual container startup.

It fails during Railway validation/configuration stage.

The issue appears to be a hidden or persisted multiRegionConfig state attached to the service.

Could you tell me now I can solve this, or:

1. Completely remove/reset multiRegionConfig from this service

2. Force the deployment into true single-region mode

3. Confirm the correct valid region for free plan deployments

4. Check whether old invalid legacy regions ("sfo", "iad") remain cached internally

Additional details:

- Docker image used: atendai/evolution-api:v2.3.5

- PostgreSQL and Redis services are online and healthy

- The issue occurs even on brand new projects

- No actual build logs are generated because deployment validation fails first

Thank you.