Bit of a weird issue here: So when working on a new test in Open mode, I'm noticing at one point the Cypress UI seems to 'hang' for a few seconds, then carries on. I've tried working through a few debugging steps but doesn't seem to be anything wrong with our website, the test code etc. I'm starting to think that it's just the Cypress UI can't keep up with the timeline updates for a lot of assertions all at the same time. I ran the same test on Run mode (headless) and watched the recording back, it does hang in the same place but much less than when running it in Open mode. Not really sure how to handle this one, I think it's safe to just commit and let the test run in CI but has anyone else experienced this or similar?

You can disable the command log for troubleshooting purposes if you like: https://docs.cypress.io/guides/references/troubleshooting#Disable-the-Command-Log This will likely make the test overall be faster (since Cypress will not be inserting DOM elements at all). But you might see if there's any slowdown at the same general point in the test flow with/without the command log.

Thanks Mark I'll give that a go