morty
09/07/2026, 1:27 PM{{ process.env }} works in Mapping expressions.
After upgrading to 0.90.2, it returns an empty value, while process.env still works correctly in Code pieces.
Environment variables are explicitly configured via:
env
AP_SANDBOX_PROPAGATED_ENV_VARS=MY_API_KEY,...
Behavior:
* Code: process.env.MY_API_KEY → ✅ works
* Mapping: {{ process.env.MY_API_KEY }} → ❌ empty
* Mapping: {{ process.env }} → ❌ empty
* Mapping: {{ process['env'] }} → ❌ empty
* v0.77.8 → Mapping access worked
There are many places in my flows that directly use expressions like {{ process.env.MY_API_KEY }}. Is there a quick way to fix this without modifying the flows?
Is this an intentional change in the Expression/Mapping evaluator, or a regression in v0.90.2? Is there a configuration to restore access to the propagated environment variables in Mapping expressions?