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.
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.
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?
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 https://crawler.algolia.com/api/1/netlify/crawl
12:31:29 AM: API answered: 200
12:31:29 AM: Your crawler is running at: https://crawler.algolia.com/admin/user_configs/*********
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
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 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?