If Cypress commands fail after cy.session(), visit the page you need after restoring the session: with testIsolation enabled, Cypress clears the page, and restoring cookies and storage does not load your app. For 401s, wrong accounts, or missing state, check that login completes before setup ends, validate authentication, and use a session ID that distinguishes every state-changing input.
What cy.session() restores—and what it does not
cy.session() saves cookies, localStorage, and sessionStorage after its setup and validation steps. When Cypress encounters the same session ID later, it can restore that browser data instead of repeating login setup. It does not cache or load the application page. See the Cypress cy.session() API reference.
As an Amazon Associate I earn from qualifying purchases.
That distinction explains the most common failure: authentication data may be restored correctly while the browser is still on a blank page. The right fix depends on whether the symptom is a blank page, an authentication failure, the wrong identity, missing storage, or an assumption about reuse across specs.
Commands fail after cy.session(): visit the page under test
When testIsolation is enabled, Cypress clears the page. After the session command, explicitly load the route your test needs before querying or interacting with the app. Cypress states: “When testIsolation is enabled, ensure that you’re calling cy.visit() after calling cy.session(), otherwise your tests will be running on a blank page.”
#1 Best Overall
beforeEach(() => {
cy.session('user', () => {
cy.visit('/login')
cy.get('[name=email]').type(Cypress.env('email'))
cy.get('[name=password]').type(Cypress.env('password'), { log: false })
cy.get('button[type=submit]').click()
cy.url().should('include', '/dashboard')
})
// Restoring a session does not visit this page for you.
cy.visit('/dashboard')
})Keep the login-success assertion in the setup callback. That proves the login flow completed before Cypress saves the session. Do not use the post-restore page as evidence that setup succeeded: it is a separate step.
With testIsolation: false, Cypress does not clear the page before setup, though it still clears cookies and storage before setup. A visit is not needed solely to reload the page after cy.session() in that configuration. Disabling isolation can let one test affect another, so it is not a universal fix; make each test’s required state explicit.
401 after restoring a session: validate authentication
A 401 usually means the restored session is no longer authenticated, or setup finished before the application had established authentication. Add a validate callback that checks a protected page or authenticated API endpoint. Cypress validates sessions both after creating one and after restoring one.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
cy.session('user', () => {
cy.visit('/login')
cy.get('[name=email]').type(Cypress.env('email'))
cy.get('[name=password]').type(Cypress.env('password'), { log: false })
cy.get('button[type=submit]').click()
cy.url().should('include', '/dashboard')
}, {
validate() {
cy.request('/api/me').its('status').should('eq', 200)
}
})
cy.visit('/dashboard')Use the endpoint and expected response that actually demonstrate authentication in your app. If validation fails on a restored session, Cypress reruns setup. If it fails immediately after setup, the test fails, exposing an incomplete login rather than silently accepting it.
Wrong user or role restored: make the ID represent the session
The session ID identifies the state produced by setup. If username, role, tenant, login method, or another changing input affects that state, include it in the ID. Otherwise Cypress can treat distinct logins as the same session and restore the wrong account.
const sessionId = {
username: Cypress.env('email'),
role: 'admin',
tenant: 'north'
}
cy.session(sessionId, () => {
// Log in as the specified identity and role.
})Cypress deterministically stringifies array and object IDs, so structured IDs are suitable. Do not put passwords, access tokens, or other secrets in the ID: IDs appear in the reporter.
Rank #3
Missing or recreated storage: inspect saved and applied data
Use the Sessions Instrument Panel and command log to tell whether Cypress created, restored, or recreated a session. This separates a cache-selection problem from data that was never fully applied.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsCypress.session.getSession(id)inspects the saved session data.Cypress.session.getCurrentSessionData()inspects the cookies and storage currently applied in the browser.
If expected attributes are absent, setup or validation may have finished before the application wrote them. Wait for a reliable application signal—such as the authenticated route, a visible signed-in element, or a successful protected request—before the session is saved. Cypress documents these inspection helpers in its session API.
Cross-spec reuse: know the cache boundary
cacheAcrossSpecs defaults to false. When enabled, its cache is in memory for one cypress run on one machine; it does not persist to disk, carry into a new run, or transfer between parallel CI machines. Each machine must establish its own session.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Specs that reuse a cross-spec session must call cy.session() consistently: use the same ID, setup, validation, and cacheAcrossSpecs value. If a later spec unexpectedly logs in again, first check whether it is in the same run and on the same machine, then compare those session definitions.
Old cookie-preservation code or subdomain surprises
Cypress.Cookies.defaults and Cypress.Cookies.preserveOnce were removed; Cypress recommends cy.session() for preserving cookies and browser storage. Check the migration notes if a test still relies on the older APIs: Cypress migration guide.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCookie commands use the hostname rather than the superdomain by default. If a test expects a cookie to be shared across subdomains, verify the cookie’s domain option instead of assuming that preservation across one host covers every subdomain.
A practical troubleshooting order
- Classify the symptom: blank page, 401, wrong identity, missing storage, or cross-spec reuse.
- Check the command log and Sessions Instrument Panel to see whether Cypress created, restored, or recreated the session.
- Make setup prove login success with an assertion before it ends.
- Add or repair
validateso it checks the authenticated state. - Build the ID from all inputs that change session state; exclude secrets.
- After
cy.session(), callcy.visit()for the route under test when isolation is enabled. - For missing data, compare saved and applied state with Cypress.session helpers and wait for the app to apply storage.
- For cross-spec behavior, verify identical session definitions and remember the one-run, one-machine boundary.
- For legacy cookie code, check the migration and the cookie domain expected by the test.
Version behavior to check
The API history records cacheAcrossSpecs as added in Cypress 10.9.0, setup as required in 11.0.0, and the experimental session-and-origin flag as removed when the command became available by default in 12.0.0. Verify examples against the Cypress version installed in your project and the current API reference, particularly when migrating older tests.
Or skip the browser setup
If your task is to capture a page rather than debug Cypress authentication, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a screenshot or PDF; its clean-shot workflow accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture, with each step configurable. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Its MCP server provides screenshot tools for AI agents, and 1,000 screenshots per month are free with no card; paid plans start at $5 for 3,000.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for parameters and response details. Sign up for 1,000 free screenshots a month, no card required.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Frequently Asked Questions
Does cy.session() restore the page I was on?
No. It restores browser cookies and storage; load the page your test needs separately.
Does cacheAcrossSpecs share a session across parallel CI workers?
No. Its cache is limited to one Cypress run on one machine.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
