## TL;DR

Keep sandbox and production connection ids in separate config and never hardcode env.

## Fix

1. Keep sandbox and production connection ids in separate config and never hardcode env.
   Expected: you can confirm this matches your situation.

## When to use

- You are setting up or using this Unified.to environments feature.
- The symptom matches: moving from Sandbox to Production.

## When NOT to use

- Unrelated Unified.to environments issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Unified.to environments.

## Variant phrasings

### moving from Sandbox to Production

## Why it happens

Unified.to uses an env parameter: build and test against Sandbox, then switch env to Production for live data.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.