high

CypressError: cy.request() failed

cy.request() failed because the server returned an error, the connection was refused, or the request timed out.

Common Causes

  1. 1API server is down or unreachable
  2. 2Authentication token is missing or expired
  3. 3Request body is malformed
  4. 4CORS configuration blocks the request
  5. 5SSL certificate issues

How to Fix

Allow failures with failOnStatusCode

cy.request({
  url: '/api/data',
  failOnStatusCode: false,
}).then((response) => {
  expect(response.status).to.eq(404);
});

When testing error cases, disable automatic failure on non-2xx status codes.

Add authentication headers

cy.request({
  url: '/api/data',
  headers: {
    Authorization: `Bearer ${Cypress.env('API_TOKEN')}`,
  },
});

Include auth headers for protected endpoints. Store tokens in Cypress environment variables.

How ObserveOne Helps

ObserveOne monitors your API endpoints 24/7 and catches errors before they impact your test suite.

Start Monitoring Free

Related Errors

CypressError: cy.visit() failed

cy.visit() failed to load the target URL. The server may be unreachable, or the response status code indicates an error.

CypressError: Timed out retrying after 4000ms

A Cypress command timed out while retrying. Cypress automatically retries assertions until the timeout, then fails. The default is 4 seconds.

CypressError: Expected to find element but never found it

Cypress could not find any element matching the selector within the timeout period. The element may not exist, may have a different selector, or may not have been rendered yet.

CypressError: element has been detached from the DOM

The element that Cypress was interacting with was removed from the DOM and re-rendered. This is common in React/Vue/Angular apps where components re-render.

AssertionError: expected true to equal false

A Chai assertion in Cypress failed because the actual value did not match the expected value. This is the most common test failure type.