Variable Precedence Between Environment and Collection in Postman 10+

Problem Context

In Postman 10 and newer, a collection may define a variable foo while the active environment also contains foo. When running the request from the main app the environment value is returned, but some users observe the collection value in the Collection Runner or a Monitor. This inconsistency can cause a configuration that works locally (using collection variables) to fail in production when the environment is expected to win.

Unresolved Decision

The Postman documentation lists a clear hierarchy (environment > global) but does not explicitly state the interaction between environment and collection scopes, nor how this rule applies in different execution contexts.

Key Questions

• Does the Collection Runner prioritize collection variables over environment variables, contrary to the documented hierarchy?
• Is there a context‑specific rule that causes monitors to resolve variables differently from the app?
• What change, if any, is required in the documentation to clarify this precedence?