Site: pesfoundationworld.org (
main--pesfoundation.netlify.app), Free plan
Function type: Standard Lambda-compatible Function (CommonJS,exports.handler), not v2/Edge
Function:netlify/functions/dialogflow-chat.jsSymptom: Any environment variable with “Contains secret values” checked resolves as
undefinedinprocess.envat Function runtime, even though the variable is correctly saved, displays properly (masked) in the dashboard, is scoped to include Functions, and its value is set for the Production deploy context matching the live site.Isolated with a controlled test: Created two throwaway variables in the same deploy — one with “Contains secret values” checked, one without, identical scope and Production value. Logged both from inside the same function invocation. The non-secret variable’s value came through correctly. The secret-flagged variable came through empty. Repeated across multiple separate invocations and two separate “Clear cache and deploy” redeploys, with identical results each time.
Ruled out before concluding this: code logic (verified exact source, checks are plain
if (!process.env.X)),netlify.toml(no variable shadowing, no[build.environment]collision, no[functions]directory mismatch), duplicate function files (none), build plugins (none), CDN/browser caching (retested via Tor Browser), stale deploy (forced clean redeploy each time), wrong deploy context (confirmed Production, confirmed correct site/domain via the Function’s own logged endpoint).Request IDs for reference: 9906d062, 27809f38, a4295c8d, d2ddc837, 45eee1b3, 7b5859d4, 98ce6d49, d162131e
Workaround: Unchecking “Contains secret values” on the affected variable resolved the issue immediately with no other change.
Question: Is this expected/known behavior for secret-flagged variables in Lambda-compatible Functions on the Free plan, or a bug? Happy to provide the site ID or any further detail if useful for reproducing.