This is being thrown from this piece of code: https://github.com/cypress-io/cypress/blob/develop/packages/driver/src/cy/commands/sessions/index.ts#L435

I haven't seen this error before, I bet it is a timing thing.

This may be similar to #25550.
However, that issue was closed, and I can't tell if there were any changes made.

Experiencing the same issue:

Failure Message: cy.then() timed out after waiting 4000ms. Your callback function returned a promise that never resolved. 
The callback function was: async () => { 
setSessionLogStatus(utils__WEBPACK_IMPORTED_MODULE_6.statusMap.inProgress(step)); 
await (0,utils__WEBPACK_IMPORTED_MODULE_6.navigateAboutBlank)(); 
await sessions.clearCurrentSessionData(); 
return cy.whenStable(() => createSession(existingSession, step)); 
} https://on.cypress.io/then 

Chrome 127, Cypress 13.7.3

Same issue here (cypress 13.15.1):
Your callback function returned a promise that never resolved. The callback function was: async () => { setSessionLogStatus(utils__WEBPACK_IMPORTED_MODULE_6_.statusMap.inProgress(utils__WEBPACK_IMPORTED_MODULE_6_.SESSION_STEPS.restore)); await (0,utils__WEBPACK_IMPORTED_MODULE_6_.navigateAboutBlank)(); await sessions.clearCurrentSessionData(); return restoreSession(existingSession); }

I run about 400 tests and see this happen ~1-2 times per-run on version 14.2.1. Seems like it's a timing issue but it frequently results in test flake for a larger test suite. Is it possible to get additional eyes on this as this seems to be a blocker long-term for us in guaranteeing test stability.

@jennifer-shehane Sorry to tag directly but this has become a huge disruption in my team. Just hoping for additional eyes or thoughts. I run 400+ tests for each PR and I see this failure at least 1-2 times per run. The workaround is to just re-run the tests which slows down the entire workflow. I've been trying to find programmatic workarounds on my end but not sure anything is possible since the failure is on the Cypress side. Open to trying anything.

I utilize session for all my authentication as well as cacheAcrossSpecs in order to minimize the amount of new sessions I create. This means for the large majority of these tests, they are restoring the session which appears to be where the issue occurs and likely why I see it so often with my large test suite.

Upgrading to 14.3.3 has improved the issue (likely due to this fix #31634) but this is still happening in my pipeline.
The frequency of this issue seemed to happen every or every-other run.
Now the frequency has decreased to ~1/10 runs.

While this is a huge improvement, I'm wondering if there's still anything to be done to fully address this issue. Thank you.

Hi @davidmatium 👋🏼, glad to see there was some improvement and yes, we should be able to fully address the issue. I'll take a look at it again soon but I'll also probably need you to run with some DEBUG logs turned on so we can get some additional info. I'll keep you updated.

@davidmatium, I built a pre-release version of Cypress (based off of v14.4.0) that includes some additional debug logging (they're automatically printed to the terminal). Could you try the new version and send me the debug logs. Thanks!