When using cypress cloud, does the --record flag communicate with https://cloud.cypress.io/ via port 443? The CI system I'm using routes all outbound traffic through a proxy and want to ensure it'll work if we open up the firewall.

Here's a list of the URLs that will need to be added to your VPN: https://docs.cypress.io/guides/references/troubleshooting#Allow-Cypress-URLs-on-VPNs Also, If your proxy does not allow the https://download.cypress.io domain, you could install the binary to help circumvent the firewall by setting

CYPRESS_BINARY_VERSION=/some/path/to/cypress.zip

as an env var: https://docs.cypress.io/guides/references/advanced-installation#Install-binary

We encountered an unexpected error talking to our servers. We will retry 3 more times in 30 seconds... The server's response was: RequestError: Error: ETIMEDOUT We encountered an unexpected error talking to our servers. We will retry 2 more times in 1 minute... The server's response was: RequestError: Error: ETIMEDOUT We encountered an unexpected error talking to our servers. We will retry 1 more time in 2 minutes... The server's response was: RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io We encountered an unexpected error talking to our servers. We will retry 0 more times in ... The server's response was: RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io Warning: We encountered an error talking to our servers. This run will not be recorded. This error will not alter the exit code. RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io We encountered an unexpected error talking to our servers. We will retry 3 more times in 30 seconds... The server's response was: RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io We encountered an unexpected error talking to our servers. We will retry 2 more times in 1 minute... The server's response was: RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io We encountered an unexpected error talking to our servers. We will retry 1 more time in 2 minutes... The server's response was: RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io We encountered an unexpected error talking to our servers. We will retry 0 more times in ... The server's response was: RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io We encountered an unexpected error talking to our servers. Because you passed the --parallel flag, this run cannot proceed because it requires a valid response from our servers. The --group flag you passed was: e2e The --ciBuildId flag you passed was: 23641 The server's response was: RequestError: Error: getaddrinfo EAI_AGAIN api.cypress.io

I saw something there is API https://docs.cypress.io/faq/questions/cloud-faq#Im-working-at-a-restrictive-VPN-Which-subdomains-do-I-have-to-allow-on, but I do not understand anything here.

So, looking at the test cancellation section of our Cloud dashboard, I see that it is only applicable to Business-level subscriptions. Considering that even on Team-level sub we are charged per-test-result, (10k included in base cost), this seems like a bit of a crap move on Cypress' behalf. With test cancellation on failures, it's clear we'd save some small amount of test results over the course of a month, but in order to get that saving we would have to spend more up-front on the next tier. Just wanted to feed back that this feels a bit crap as a customer, making Teams-sub level feel like a bit of a 2nd-class citizen. This is likely intentional, but leaves a bad taste in the mouth.

When setting the parallel: true in the workflow, I am getting "Error: Resource not accessible by integration" Error.

Im using github actions + cypress cloud for keeping results and reporting test to slack channel. Is it possible to change slack message format and color? I need to mark build as green if there're less than N failures

Links still say "View run in Dashboard" and to refer to Cypress Dashboard for project settings Also found in PRs for the Cypress repo: https://github.com/cypress-io/cypress/pull/25555 Didn't think it was big enough to make an issue about, but a would-be-nice for updating. Thanks!

@gray-kilobyte-89541 When I run npx cypress run command frequently I'm getting the below error from the screenshot, due to this I'm unable to run the test, please provide me a solution. I'm using mochawesome for reporting as you see in the second screenshot.

We have a monorepo, 4 e2e test suites and 4 projects with 4 different record keys. Is there a way to consolidate everything to one key? I couldn't find anything in the docs.

need to sign in to a microsoft account SSO. I cannot find a working tutorial online. when having cypress click the login button on the page, the login page does not load.

The slack integration for cypress.io was updated today and it removed tags from the slack message. We heavily use the tags to tag runs between environments. This is a major issue for our org's QE department

Hello there, I have just released the new version of cypress to the team that has the cypress runner debug integration. As regards the slack channel integration, is there a config to show the branch name and perhaps a link to the GH run itself?

We recently increased our retries to "runMode: 2" from 1. We'd like to be able to measure if many tests actually end up passing on the 2nd retry vs the first to give us an idea if the increase made much of a difference. I haven't found a good way to do this after looking through the cloud UI and reading the docs some. Is it possible beyond going through individual flake instances to see how many attempts were made?

I tryed to integrated cypress app with gitlab, but when i input appliationID and secret i get redirected to gitlab.com and when asked to login its invalid username, because the gitlab we use is shared on private domain like "gitlab.company.com" and accounts are not viable in gitlab.com. Am i doing something wrong?

I upgraded to 12.5 from 9.7 and when I log into cypress dashboard and click on a project, I see the following in my left hand navigation panel: latest runs, branches, analytics, project settings I do not see Debug which in the documentation should be under Runs (or latest runs I guess?) What do I have to do to enable this feature? I'm not an admin, but I'm responsible for it. But it's hard to get help without knowing what to ask them to do.

I have a framework where i am storing the results in a JSON and XLSX file during the runtime . Is there a possibility to include these in cypress cloud along with screenshots and videos ?

Hi folks, we are running pipeline with apprx. 400 tests, 7 group of parallels. There are some errors on found on server logs. We know the error time, but how to check which test cause it ? How to see the test start or end time on cloud ?

Will this be added?

So we've had a number of runs get 'stuck' and last a couple of hours before timing out or otherwise failing, due to weird environment issues. I'm not sure why they went on for hours tbh as they should surely have timed out before that but anyway that's another issue to follow up. My question is, can I easily archive many runs within a project branch at once? At the moment I'm having to scan through every run for ones >1hr run time, click into them, click the archive button, go back and find the next one. Would be great if there was an option on the run overview screen where I could use a multi-select and then perform an action like archive across many runs at once if such a thing doesn't already exist. Thanks 🙂

Since my company decided to get rid of our Google accounts, I cannot login to the Cypress cloud anymore. I tried resetting the password, since I still have the same email, but I don't receive the password-reset mail. Is there any other way to reset the password or something similar?

When I attempt to go to my org's settings page I am either getting redirected to my organizations page or a 50x error page.

xpected Error - Redirecting to /organizations Error: Network error: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at new t (apollo-client.esm.js:875:28)

Can someone help me to understand the causes to fail the test on CI? All my tests get passed when I run locally, I have implemented the GitHub action to run tests on push there is no issue with installing dependencies but the issue is that some tests are failing. Both local and CI use the same specs:  chrome version

chrome 112

, cypress version (12.9.0), and node(14.21.0). Difference: Github action I used parallel. One error I found is:

Failed to save: Unable to reserve cache with key yarn-linux-x64-somekey, another job may be creating this cache. More details: Cache already exists. Scope: refs/heads/qa/development, Key: yarn-linux-x64-

Any possible reasons?

name: cypress-schedule-run

on:
  schedule:
    - cron: '*/5 * * * *'
  workflow_dispatch:

jobs:
  my-job:
    runs-on: ubuntu-latest
    steps:
      - name: first step
        run: echo "hello"

I have added this code to my action file to run the job every 5 minutes but the job doesn't run at all. And workflow_dispatcher event is also not there. Any solution?

Here is my issue: Trying to install the Cypress Dashboard for my project. When enter the Record key in terminal getting the error as in screenshot. In my project support file (index.js) is not under the Cypress/support. But we are using e2e.ts as a support file which is under the projectname/e2e/src/support/e2e.ts. But it is not recognized the current e2e.ts file, although I have updated the support File location as well. But no luck.

I am automating a test case in Cypress but what I observed is after making changes in locators or a statement in Cucumber feature file its not identifying new changes. Can anyone help me with this issue please? #1064946933187235880

Can we customize the Cypress dashboard(Organization) project access? Currently, any invited users in an Organization can view all the projects inside that particular organization. For a certain reason, I want to invite users and give access to only selected projects.

On schedule run there is no prproper message and the contributor also not available. How to have some custom message for schedule run?

Is there a way to make cypress tests to report chromium renderer crash instances to the cypress cloud? This can be really useful in analysing the test pipeline failures.

I have a question from one of our consultants at Xebia: is it possible to make use of the Cypress Cloud but in a European Datacenter ?