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

# BEST-PRAC-2 (GitLab) — Job has no timeout

> A stuck job can run until the project/instance maximum, wasting runner minutes and holding resources. Set an explicit per-job or default `timeout:`.

| Field    | Value                                                                                                 |
| -------- | ----------------------------------------------------------------------------------------------------- |
| Category | `BEST-PRAC-2`                                                                                         |
| Platform | GitLab CI                                                                                             |
| Severity | **LOW**                                                                                               |
| Auto-fix | Flags jobs without a `timeout:` that also don't inherit one from a `default: { timeout: ... }` block. |

## What the check does

A stuck job can run until the project/instance maximum, wasting runner minutes and holding resources. Set an explicit per-job or default `timeout:`.

## Why it matters

Findings for this rule fire only on `.gitlab-ci.yml` and `.gitlab-ci/*.yml`.
It is the GitLab analog of the correspondingly-numbered GitHub Actions rule; see
the [rules overview](/rules/overview#gitlab-ci-workflow-checks) for the full
GitLab table.