Netlify Build Complete but receiving "Command did not finish within the time limit" on paid plan

Hi, @STACKINJAM. If you tell us the site subdomain or the site API ID, our support team can extend the build time limit for the site.

However, it sounds more like the following issue is occurring:

If this is issue (a stuck build), manually closing any connections to sites or databases being made during the site build process is the solution. If there are other questions or concerns, please let us know.

Thanks for the reply luke!

I think it is getting stuck due to time since when I had only 3 products that it was pulling from shopify it would work just fine but now that there are 100 it is timing out. I tested on another provider and it is deploying fine. Please take a look at your convenience.

The most recent build contains this:

9:51:51 AM: warning Browserslist: caniuse-lite is outdated. Please run:
9:51:51 AM: npx browserslist@latest --update-db
9:53:44 AM: success Building production JavaScript and CSS bundles - 114.413s
9:53:45 AM: success Rewriting compilation hashes - 0.001s
9:54:30 AM: success run queries - 189.991s - 155/157 0.83/s
10:12:14 AM: success Building static HTML for pages - 15.049s - 142/142 9.44/s
10:12:14 AM: success Generating image thumbnails - 1253.392s - 3480/3480 2.78/s
10:12:14 AM: info Generated public/sw.js, which will precache 7 files, totaling 747583 bytes.
10:12:14 AM: The following pages will be precached:
10:12:14 AM: /offline-plugin-app-shell-fallback/index.html
10:12:14 AM: success onPostBuild - 0.083s
10:12:14 AM: info Done building in 1267.379983669 sec
10:12:14 AM: Done in 1267.69s.
10:12:14 AM: ​
10:12:14 AM: (build.command completed in 21m 7.9s)

The default timeout for a site build is 15 minutes so this was an expected timeout, not a stuck build. Would you like for us to extend the build time limit to 30 minutes for this site?

Yes, please increase the build time. Thank you!

Hello, please increase our build timeout to 30 minutes as well

hi, which netlify site name is this regarding?

pedantic-gates-b75f4f, I have opened a zendesk ticket as well

Thanks! Just got that bumped for you.

1 Like

Hello! I need help extending build time to 30 minutes for center-site-app-prod ( Thanks!

Hi @fejiroofficial,

It appears that this has already been done.

I have the same issue, and it is because Algolia plugin spents hours to reindex. Without this plugin, build takes 5-6 minutes, and deploy takes about 15-25 minutes. About 20k+ pages.

12:31:28 AM: ────────────────────────────────────────────────────────────────
12:31:28 AM:   3. @algolia/netlify-plugin-crawler (onSuccess event)          
12:31:28 AM: ────────────────────────────────────────────────────────────────
12:31:28 AM: ​
12:31:28 AM: Algolia Netlify plugin started
12:31:28 AM: Sending request to crawl
12:31:29 AM: API answered: 200
12:31:29 AM: Your crawler is running at:*********
12:31:29 AM: Done.
12:31:29 AM: ​
12:31:29 AM: (@algolia/netlify-plugin-crawler onSuccess completed in 501ms)
12:31:29 AM: ​
12:31:29 AM: ────────────────────────────────────────────────────────────────
12:31:29 AM:   Netlify Build Complete                                        
12:31:29 AM: ────────────────────────────────────────────────────────────────
12:31:29 AM: ​
12:31:29 AM: (Netlify Build completed in 20m 32.9s)
12:31:29 AM: Execution timed out after 20m48.25470842s
12:31:29 AM: Error running command: Command did not finish within the time limit
12:31:29 AM: Failing build: Failed to build site
12:31:29 AM: Finished processing build request in 20m56.624569156s

Hey there, @FuadEfendi :wave:

Would you like us to increase the build timeout limit for you? Let me know.

Hi @hillary

No needed; thank you for suggesting! Nothing fails, only incorrect log message, site gets published.

It is Algolia crawler, it takes about 2-3 hours to crawl 10,000 pages (which is very good speed for “robot”), they have to fix their plugin reporting.

I am Ok; and I am implementing direct data injection to Algolia, which takes few seconds for 10,000 documents.

1 Like

Thanks for coming back and letting us know. Happy building!

1 Like

hello, i have the same error
Error executing command: The command did not complete within the time limit
on my website

Hi @thiagowho42

I’m afraid I’m not finding the site in question. I do see another site that could be this one but was renamed? I do see a deploy failure due to timeout on that site but it also appears that there have been a couple of successful deploys since then. Assuming the ‘old…’ site :wink: is the correct one, I’ve gone ahead and increased the build timeout to 30 minutes.

Could you let us know if that wasn’t the right site or if you’re still exceeding the built time limit?

Hi there! I’m currently experiencing the same issue and haven’t heard anything back from the support team yet. Would anyone here be able to increase my build time limit please? I’ve just migrated my client’s production sites over from Gatsby Cloud and need to get everything up and running as soon as possible.

Thanks in advance!

@pixelsmatter, no duplicate posts please: “No Gatsby cache found. Building fresh” every time - Support / Build Plugins - Netlify Support Forums

Gatsby Cloud refugee here - I’m running into this issue as well :frowning: No successful builds on Netlify even though on our paid Gatsby Cloud plan, our site is fine.

Here’s a link to the latest failed deploy: Netlify App

The last few log messages are:

11:32:50 AM: Execution timed out after 18m10.00223901s
11:32:50 AM: Error running command: Command did not finish within the time limit
11:32:50 AM: Failing build: Failed to build site
11:32:51 AM: Finished processing build request in 18m43.185s

Please boost our time limit so I can see if it fixes our failing builds. We can’t migrate from Gatsby Cloud until this is resolved.

Hi @tqureshi-uog

I checked your latest build and based on what I found, I don’t think the issue is the build timelimit, rather it is an out of memory error. I’m referring to this:

2:14:16 PM: URL path: /gceb3/
12:14:16 PM: Killed
12:14:16 PM: ​
12:14:16 PM: build.command failed                                        
12:14:16 PM: ────────────────────────────────────────────────────────────────
12:14:16 PM: ​
12:14:16 PM:   Error message
12:14:16 PM:   Command failed with exit code 137: npm run build (

And when I view the memory usage for your build, I see that you are maxing out the memory:

Take a look at this support guide for information on how to troubleshoot this issue: [Support Guide] What can I do if my build fails for memory-overallocation-related errors?

I hope this helps!

1 Like