---
title: "Test failing with 4XX/5XX response in transaction test"
slug: "test-failing-with-4xx5xx-response-in-transaction-test"
updated: 2025-06-27T19:22:58Z
published: 2025-06-27T19:22:58Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test failing with 4XX/5XX response in transaction test

## Overview

In Transaction Tests, the first request in each step is considered to be the primary request for that step. When a primary request fails with a 40x/50x error, this results in a test failure, whereas a failure of a child request within the step would not result in test failure.

This makes sense when the primary request is an HTML file, but sometimes, depending on how you break your script up into steps, the primary request for a step might be a css, img, or js file. In such cases, you might not want the test to fail.

![kb_40x.png](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/360094643971-kb_40x.png)

## Workaround

To mitigate this issue, apply a request block to that request, or enable **Treat 40X and 50X as successful** in the test's **Additional Settings**.

## See also

Advanced Settings: [https://docs.catchpoint.com/docs/advanced-settings](https://docs.catchpoint.com/docs/advanced-settings)

Request Override: [https://docs.catchpoint.com/docs/request-override-guide](https://docs.catchpoint.com/docs/request-override-guide)