# GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds

**Code:** `execution took longer than 1h0m0s` · **Category:** CI/CD · **Seen on:** GitLab CI

The job ran past its timeout (project default is 60 minutes) and GitLab killed it.

## Meaning

Hung processes and interactive prompts are the usual cause. Set a realistic `timeout:` on slow jobs, make commands non-interactive, and find the step that stalls using timestamps in the log. Runners can also impose a maximum job timeout that overrides the project setting.

## Common causes

- Command waiting for input or a lock
- Network call without timeout
- Tests deadlocked or very slow on a small runner
- Service container never healthy
- Project/runner timeout set lower than the job needs

## Quick fix

1. Add `timeout: 30m` per job to fail fast, or raise it for long builds
2. Run steps non-interactively and with explicit timeouts
3. Check the runner's maximum job timeout

## Detailed fix by platform

### GitLab CI

1. Settings → CI/CD → General pipelines → Timeout
2. Use `script: - timeout 20m ./long-task.sh`

## Code examples

### Per-job timeout

```yaml
integration:
  timeout: 30m
  script:
    - timeout 25m ./run-integration.sh
```

## How to diagnose

1. **Last output** — Where did the log stop?
2. **Prompt** — Waiting for input?
3. **Limits** — Job vs runner timeout?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/cicd/gitlab-job-timeout-execution-took-longer)