Incident Dossier

Region Fallback Shadow

A deploy reads its target region first from the bundled config file and only falls back to the environment when nothing is set. The config file ships with a default region for the build farm, so the orchestrator's override never reaches the deploy and traffic is pinned to the wrong cloud.

Initial failing signalenv.REGION override is shadowed by config.regionExpected behavior: resolveRegion({ config, env: { REGION: 'eu-west-1' } }) === 'eu-west-1' · actual behavior: resolveRegion({ config, env: { REGION: 'eu-west-1' } }) === 'us-east-1'

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Inspect the helper that composes the target region.
Notice the order in which the config file and env are consulted.
Confirm the failure when the config file carries a baked-in default.
Make the smallest correction so the orchestrator override wins.

Focus Mode

Start

src/region.js

Likely area

src/region.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicDeployment

DifficultyMedium

Est. time15 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace