# The build ran out of time How to fix it.

URL: https://antideploy.com/blog/build-ran-out-of-time

Builds are given 20 minutes. If yours runs longer, a step is hanging or the project needs more than is allowed.

**What you see**

```
The build ran out of time. Builds are given 20 minutes, so something in the
install or build step is hanging, or this project needs more than we
currently allow.
```

## At a glance

- **What it means**: The build hit its time limit
- **The limit**: 20 minutes
- **Likely cause**: A command that never ends
- **Fix**: Make every build command finish

Published 7 October 2026. Facts checked 7 October 2026. 1 min read.

## What it means

A build that runs for 20 minutes is stopped. Most builds take a small fraction of that, so a build that reaches the limit is almost always stuck, not slow.

## Common causes

- **A command that never ends.** A build script that starts a development server or a watcher, for example `vite build --watch` or `next dev`, waits forever.
- **A package compiling from source.** A Python or native package without a prebuilt wheel can compile for a very long time. See [Failed building wheel](https://antideploy.com/blog/failed-building-wheel).
- **A step waiting for the network.** A download or a prompt that waits for input.
- **A very large project.** A build that does a great deal of work.

## How to fix it

### 1. Read the end of the build log

It shows the step that was running when time ran out.

### 2. Make every build command finish

The `build` script must exit on its own. Remove watch flags and anything that waits for input.

### 3. Prefer prebuilt packages

Pin versions and a Python version that have prebuilt wheels, so nothing compiles from source.

## Build time questions, answered.

Anything else? Write to us and a person answers.

[support@antideploy.com](mailto:support@antideploy.com)

### Can I get more time?

Builds are given 20 minutes today. Shrinking or fixing the step is the way forward.

### Does this failed deploy cost anything?

No. Failed deploys never count against your plan.

### How do I find the step that hung?

Read the end of the build log. It shows the step that was running when time ran out. Your agent can read it from the deploy history.

## More guides, and the platform.

Each platform page covers one part of Antideploy: what it does, where it stops and the questions people ask. [See the whole platform](https://antideploy.com/platform), or [all the guides](https://antideploy.com/blog).

- [FATAL ERROR: JavaScript heap out of memory](https://antideploy.com/blog/javascript-heap-out-of-memory-during-the-build): The build ran out of memory, usually from a very large bundle. Shrink it or raise Node's limit.
- [ERROR: Failed building wheel for psycopg2](https://antideploy.com/blog/failed-building-wheel): A package had to be compiled and the compile failed. Use a prebuilt version, or pin Python to 3.12.
- [How to let your agent read logs and fix a failed deploy](https://antideploy.com/blog/how-to-let-your-coding-agent-read-logs-and-fix-a-failed-deploy): The loop: read the reason, read the logs, fix the code, deploy again. And what Antideploy repairs for you.

- [Deployments](https://antideploy.com/platform/deployments)
- [Logs and monitoring](https://antideploy.com/platform/logs-and-monitoring)

Facts on this page were checked against the live platform on 7 October 2026.

## Deploy something. Start with one sentence.

Paste one sentence into your coding agent, click Approve once, and get a live link. No card, no trial clock.

To set this up, give your coding agent this sentence:

```text
Set this project up to deploy on Antideploy. Fetch https://antideploy.com/agent.md and follow it.
```