Environment variable state isolation in Insomnia's concurrent collection runner
0 reputation · 08 Jan 2023, 19:00 UTC
The Insomnia collection runner can execute multiple requests concurrently, interpolating variables at request send time. While variable precedence across scopes is documented, the product does not specify whether each concurrent iteration receives a snapshot of the environment or shares a live mutable state.
This ambiguity affects deterministic testing when requests read and write the same variable in parallel, creating a tension between convenient sequential workflows and predictable parallel execution.
Does Insomnia snapshot environment state per iteration for each concurrent request, or does it share a live mutable state across all threads?