---
title: "Enforce Failure Time Limit Impact"
slug: "enforce-failure-time-limit-impact"
updated: 2025-06-13T20:31:21Z
published: 2025-06-13T20:31:21Z
canonical: "docs.catchpoint.com/enforce-failure-time-limit-impact"
---

> ## 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.

# Enforce Failure Time Limit Impact

## Overview

Catchpoint provides an option to enforce failure on a particular test step if it doesn’t pass within a specified time limit. By default, if a step takes more than 30 seconds to load, the test fails.

There can be an impact on point usage by changing the **Enforce failure if the test run is longer than** value, as the number of objects loaded during each test-run may change. Point consumption is dependent on the actual *usage* of the features enabled, not just whether they are enabled. See example scenarios and their impact on points usage below.

## Examples

### Scenario 1:

**Enforce failure if test run is longer than 20 seconds/step**

- If a step finishes loading the full page and meets the completion condition within 20 seconds, it passes.
- If it fails to load the full page within 20 seconds, it fails.

Suppose your contract specifies a discount for tests which load fewer than 51 objects. If 60 objects would have loaded within a 30 second period, but only 40 objects were loaded before the 20 second time-out, then this change would result in a reduction in points consumed.

### Scenario 2:

**Enforce failure if the test run is longer than 60 seconds/step**

- Rather than failing after 30 seconds, a test-run continues to run until the 60th second, and loads many more objects.

If this results in objects loaded beyond the discount threshold, then point usage will increase as a result of this change.