[Bitbucket docs and community]: a step that times out after 120 minutes or runs out of memory at 4GB needs max-time and size: 2x gives 8GB, 4x gives 16GB. Validate the pipeline YAML locally with the bitbucket-pipes-toolkit before debugging config. If the build fails in Pipelines but works locally in Docker, clear the caches and rerun: stale caches with old dependencies are a classic cause. Pipe failures usually mean missing required pipe variables: check the pipe's required list.

Context: Default step limits are 2 hours and 4GB. Builds that hit them need bigger steps or smaller work.

## Matched source
Source: Source: https://support.atlassian.com/bitbucket-cloud/kb/troubleshoot-failed-bitbucket-pipelines-locally-with-docker/
Original query: "Bitbucket Pipelines step timeout: bump max-time and size, or clear stale caches"
Key terms: bitbucket, bump, caches, clear, pipelines, size, stale, step, time, timeout