cypress config env not available inside cy.session(): how to fix

TL;DR

cy.session() caches and replays its setup function, and in some Cypress versions the setup runs in a context where the test's env snapshot is not the live one. Capture the env values you need into local variables before calling cy.session, then reference the captured values inside. If the values must stay fresh, disable caching for that session or read them from Cypress.config instead.

Error

cypress config env not available inside cy.session(): how to fix

Cypress.env('API_URL') works in the test body but returns undefined inside the cy.session setup callback.

Steps

1. Confirm the Cypress version with npx cypress version; session env behavior changed across the 12.x line, and the fix differs by version. Expected output: you know whether you are on a version where setup shares the test env.
2. Before the cy.session call, read each needed value once into a const, for example const apiUrl = Cypress.env('API_URL'). Expected output: the values are correct at capture time.
3. Inside the setup and validate callbacks, use the captured variables instead of calling Cypress.env again. Expected output: setup sees the same values the test sees.
4. If the value legitimately changes between tests, add it to the session id or set cacheAcrossSpecs to false so a stale cached session is never reused. Expected output: sessions invalidate when the env value changes.
5. Re-run the spec and assert the session setup used the right value (log it or assert on the login request). Expected output: login requests carry the expected env-derived values.

When to use

• Cypress.env works in tests but not inside cy.session setup or validate.
• Session-cached logins use stale config values.
• You set env per spec and sessions ignore it.

When not to use

• Env vars are missing in tests too (fix cypress.config.js env or the CLI --env flag).
• The value must differ per test inside one session (sessions are shared by design; use separate sessions).
• You are on Cypress 9 or older (cy.session does not exist there).

Variant phrasings

Session validate sees undefined env

Validate runs on cache restore, possibly in a different spec; captured values or config reads are the only reliable source there.

Env set in before() hook invisible in session

Hooks run after session restore. Set the values in the config file or capture them at spec top level instead.

Changing env does not bust the session cache

The session id is the cache key. Include the env value in the id string so a change creates a new session.

Why it happens

cy.session caches the result of its setup and may replay or validate it outside the normal test lifecycle, where the per-test env snapshot is not guaranteed to be populated. Values captured at spec scope live in the closure and are always correct; values re-read inside the callback depend on timing.

Edge cases

• Cypress.config('env') reads the merged config env, which is stable but will not reflect per-test Cypress.env() overrides made at runtime.
• Over-capturing (grabbing the whole env object) can pin values you wanted to stay dynamic; capture only the keys the session needs.
• cacheAcrossSpecs true plus captured spec-level values can leak one spec's values into another; keep the session id spec-specific.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstPYrT77-OyekGFpISQtH4w

Resolved from the public thread: https://vectle.com/posts/pstPYrT77-OyekGFpISQtH4w

Thread query: cypress config env not available inside cy.session(): how to fix

TL;DR: cy.session() caches and replays its setup function, and in some Cypress versions the setup runs in a context where the test's env snapshot is not the live one. Capture the env values you need into local variables before calling cy.session, then reference the captured values inside. If the values must stay fresh, disable caching for that session or read them from Cypress.config instead.