# Gatsby build takes too long (went from 5m to 30m) - Execution timed out after 18m - Still builds **URL:** \ **Category:** Support\ **Tags:** deployment\ **Created:** [March 6, 2022, 7:55pm UTC](https://answers.netlify.com/t/gatsby-build-takes-too-long-went-from-5m-to-30m-execution-timed-out-after-18m-still-builds/52971 "2022-03-06T19:55:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![aburuqayyah](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/aburuqayyah/32/26625_2.png) [@aburuqayyah](https://answers.netlify.com/u/aburuqayyah)\ **Post date:** [March 6, 2022, 7:55pm UTC](https://answers.netlify.com/t/gatsby-build-takes-too-long-went-from-5m-to-30m-execution-timed-out-after-18m-still-builds/52971/1 "2022-03-06T19:55:40Z")
Hi, my site usually builds in 5m. **SITE:** [https://dvlp-securiwiser.netlify.app/](https://dvlp-securiwiser.netlify.app/) After I added more content (+150 mdx files, on top of existing 200-ish), the build started failing every time on Netlify (works with local gatsby build). Than, I refactored the code to more efficient queries and updated dependencies. Also added `NODE_OPTIONS = "--max_old_space_size=4096"` to netlify.toml. Now the site builds, but it takes a huge amount of time (20-30m). There’s a warning about slow queries but I can’t find a problem with them. It builds just barely. As in, there’s a failed build message but than it proceeds and still builds. After “5. Deploy Site” just below the “Netlify Build Complete” heading, I get this message: > 4:52:55 PM: (Netlify Build completed in 16m 46.8s) > 4:52:55 PM: Execution timed out after 18m8.43859981s > 4:52:55 PM: Error running command: Command did not finish within the time limit > 4:52:55 PM: Creating deploy upload records > 4:52:56 PM: Failing build: Failed to build site > 4:52:56 PM: Failed during stage ‘building site’: Command did not finish within the time limit > 4:52:56 PM: Finished processing build request in 18m16.010323949s but than the build still finishes and the site is live… **Build settings:** > > Base directory: Not set > > Build command: npm run build > > Publish directory: public > > Builds: Active **Full log:** > 4:34:37 PM: Build ready to start > > 4:34:40 PM: build-image version: 122b31996ccaffd45d820a452d6227f8312110cc (focal) > > 4:34:40 PM: build-image tag: v4.5.3 > > 4:34:40 PM: buildbot version: c68dbedb54f97d2ade6b8aa44f524f50c2bf9351 > > 4:34:41 PM: Fetching cached dependencies > > 4:34:41 PM: Failed to fetch cache, continuing with build > > 4:34:41 PM: Starting to prepare the repo for build > > 4:34:41 PM: No cached dependencies found. Cloning fresh repo > > 4:34:41 PM: git clone > > 4:34:45 PM: Preparing Git Reference pull/11/head > > 4:34:46 PM: Parsing package.json dependencies > > 4:34:47 PM: Starting build script > > 4:34:47 PM: Installing dependencies > > 4:34:47 PM: Python version set to 2.7 > > 4:34:47 PM: Downloading and installing node v16.14.0… > > 4:34:48 PM: Downloading nodejs. org/dist/v16.14.0/node-v16.14.0-linux-x64.tar.xz… > > 4:34:48 PM: Computing checksum with sha256sum > > 4:34:48 PM: Checksums matched! > > 4:34:51 PM: Now using node v16.14.0 (npm v8.3.1) > > 4:34:51 PM: Started restoring cached build plugins > > 4:34:51 PM: Finished restoring cached build plugins > > 4:34:51 PM: Attempting ruby version 2.7.2, read from environment > > 4:34:52 PM: Using ruby version 2.7.2 > > 4:34:52 PM: Using PHP version 8.0 > > 4:34:52 PM: Started restoring cached node modules > > 4:34:52 PM: Finished restoring cached node modules > > 4:34:53 PM: Installing NPM modules using NPM version 8.3.1 > > 4:35:11 PM: npm WARN deprecated source-map-url 0.4.1: > > 4:35:11 PM: npm WARN deprecated urix 0.1.0: Please see > > 4:35:11 PM: npm WARN deprecated resolve-url 0.2.1: > > 4:35:11 PM: npm WARN deprecated source-map-resolve 0.5.3: See > > 4:35:11 PM: npm WARN deprecated uuid 3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See > > 4:35:11 PM: npm WARN deprecated uuid 3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See > > 4:35:11 PM: npm WARN deprecated uuid 3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See > > 4:35:14 PM: npm WARN deprecated redux-devtools-extension 2.13.9: Package moved to redux-devtools/extension. > > 4:35:14 PM: npm WARN deprecated querystring 0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. > > 4:35:17 PM: npm WARN deprecated subscriptions-transport-ws 0.9.19: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see For general help using `graphql-ws`, see > > 4:35:22 PM: npm WARN deprecated types/vfile-message 2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed. > > 4:35:23 PM: npm WARN deprecated puppeteer 3.3.0: Version no longer supported. Upgrade to latest > > 4:35:28 PM: npm WARN deprecated querystring 0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. > > 4:35:37 PM: npm WARN deprecated svgo 1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x. > > 4:36:06 PM: added 2452 packages, and audited 2659 packages in 1m > > 4:36:06 PM: 385 packages are looking for funding > > 4:36:06 PM: run `npm fund` for details > > 4:36:06 PM: 58 vulnerabilities (1 low, 13 moderate, 42 high, 2 critical) > > 4:36:06 PM: To address issues that do not require attention, run: > > 4:36:06 PM: npm audit fix > > 4:36:06 PM: To address all issues possible (including breaking changes), run: > > 4:36:06 PM: npm audit fix --force > > 4:36:06 PM: Some issues need review, and may require choosing > > 4:36:06 PM: a different dependency. > > 4:36:06 PM: Run `npm audit` for details. > > 4:36:06 PM: NPM modules installed > > 4:36:07 PM: Started restoring cached go cache > > 4:36:07 PM: Finished restoring cached go cache > > 4:36:07 PM: go version go1.16.5 linux/amd64 > > 4:36:07 PM: go version go1.16.5 linux/amd64 > > 4:36:07 PM: Installing missing commands > > 4:36:07 PM: Verify run directory > > 4:36:08 PM: ​ > > 4:36:08 PM: ──────────────────────────────────────────────────────────────── > > 4:36:08 PM: Netlify Build > > 4:36:08 PM: ──────────────────────────────────────────────────────────────── > > 4:36:08 PM: ​ > > 4:36:08 PM: ❯ Version > > 4:36:08 PM: netlify/build 26.3.14 > > 4:36:08 PM: ​ > > 4:36:08 PM: ❯ Flags > > 4:36:08 PM: baseRelDir: true > > 4:36:08 PM: buildId: 6224cebcb576c90008b958f4 > > 4:36:08 PM: deployId: 6224cebcb576c90008b958f6 > > 4:36:08 PM: ​ > > 4:36:08 PM: ❯ Current directory > > 4:36:08 PM: /opt/build/repo > > 4:36:08 PM: ​ > > 4:36:08 PM: ❯ Config file > > 4:36:08 PM: /opt/build/repo/netlify.toml > > 4:36:08 PM: ​ > > 4:36:08 PM: ❯ Context > > 4:36:08 PM: deploy-preview > > 4:36:08 PM: ​ > > 4:36:08 PM: ❯ Installing plugins > > 4:36:08 PM: - netlify/plugin-gatsby 2.1.2 > > 4:36:22 PM: ​ > > 4:36:22 PM: ❯ Loading plugins > > 4:36:22 PM: - netlify/plugin-gatsby 2.1.2 from Netlify app > > 4:36:23 PM: ​ > > 4:36:23 PM: ──────────────────────────────────────────────────────────────── > > 4:36:23 PM: 1. netlify/plugin-gatsby (onPreBuild event) > > 4:36:23 PM: ──────────────────────────────────────────────────────────────── > > 4:36:23 PM: ​ > > 4:36:23 PM: No Gatsby cache found. Building fresh. > > 4:36:23 PM: ​ > > 4:36:23 PM: ( netlify/plugin-gatsby onPreBuild completed in 10ms) > > 4:36:23 PM: ​ > > 4:36:23 PM: ──────────────────────────────────────────────────────────────── > > 4:36:23 PM: 2. Build command from Netlify app > > 4:36:23 PM: ──────────────────────────────────────────────────────────────── > > 4:36:23 PM: ​ > > 4:36:23 PM: $ npm run build > > 4:36:24 PM: \> gatsby-starter-default 0.1.0 build > > 4:36:24 PM: \> gatsby build > > 4:36:26 PM: success compile gatsby files - 0.970s > > 4:36:26 PM: info The following flags are active: > > 4:36:26 PM: - PARALLEL\_SOURCING · EXPERIMENTAL · (Umbrella Issue )) · Run all source plugins at the same time instead of serially. For sites with multiple source plugins, this can speedup sourcing and transforming considerably. > > 4:36:26 PM: Some features you configured with flags are used natively now. > > 4:36:26 PM: Those flags no longer have any effect and you can remove them from config: > > 4:36:26 PM: - LMDB\_STORE · EXPERIMENTAL · (Umbrella Issue· Store nodes in a persistent embedded database (vs in-memory). Lowers peak memory usage. Requires Node v14.10 or above. > > 4:36:26 PM: There are 2 other flags available that you might be interested in: > > 4:36:26 PM: - PRESERVE\_FILE\_DOWNLOAD\_CACHE · (Umbrella Issue · Don’t delete the downloaded files cache when changing gatsby-node.js & gatsby-config.js files. > > 4:36:26 PM: - DETECT\_NODE\_MUTATIONS · Diagnostic mode to log any attempts to mutate node directly. Helpful when debugging missing data problems. See > > 4:36:26 PM: success load gatsby config - 0.098s > > 4:36:27 PM: warning Plugin gatsby-plugin-advanced-sitemap is not compatible with your gatsby version 4.9.1 - It requires gatsby ^3.0.0 > > 4:36:27 PM: warning Plugin gatsby-plugin-advanced-sitemap is not compatible with your gatsby version 4.9.1 - It requires gatsby ^3.0.0 > > 4:36:28 PM: success load plugins - 1.367s > > 4:36:28 PM: success onPreInit - 0.004s > > 4:36:28 PM: success initialize cache - 0.090s > > 4:36:28 PM: success copy gatsby files - 0.143s > > 4:36:28 PM: success Compiling Gatsby Functions - 0.186s > > 4:36:28 PM: success onPreBootstrap - 0.196s > > 4:36:28 PM: success createSchemaCustomization - 0.007s > > 4:36:49 PM: success Checking for changed pages - 0.000s > > 4:36:49 PM: success source and transform nodes - 20.738s > > 4:36:49 PM: info Writing GraphQL type definitions to /opt/build/repo/.cache/schema.gql > > 4:36:50 PM: success building schema - 0.847s > > 4:36:50 PM: success createPages - 0.296s > > 4:36:50 PM: success createPagesStatefully - 0.154s > > 4:36:50 PM: info Total nodes: 2909, SitePage nodes: 379 (use --verbose for breakdown) > > 4:36:50 PM: success Checking for changed pages - 0.000s > > 4:36:50 PM: success onPreExtractQueries - 0.000s > > 4:36:54 PM: success extract queries from components - 3.913s > > 4:36:54 PM: success write out redirect data - 0.001s > > 4:36:55 PM: success Build manifest and related icons - 0.238s > > 4:36:55 PM: success onPostBootstrap - 0.240s > > 4:36:55 PM: info bootstrap finished - 30.990s > > 4:36:55 PM: success write out requires - 0.007s > > 4:37:21 PM: warning [deprecated default-site-plugin] node.fs is deprecated. Please set “resolve.fallback.fs = false”. > > 4:38:09 PM: warning chunk styles [mini-css-extract-plugin] > > 4:38:09 PM: Conflicting order. Following module has been added: > > 4:38:09 PM: \* css ./node\_modules/css-loader/dist/cjs.js??ruleSet[1].rules[11].oneOf[1].use[1]!./node\_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[11].oneOf[1].use[2]!./node\_modules/sass-loader/dist/cjs.js??ruleSet[1].rules[11].oneOf[1].use[3]!./src/components/blogDetail/style/description.scss > > 4:38:09 PM: despite it was not able to fulfill desired ordering with these modules: > > 4:38:09 PM: \* css ./node\_modules/css-loader/dist/cjs.js??ruleSet[1].rules[11].oneOf[1].use[1]!./node\_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[11].oneOf[1].use[2]!./node\_modules/sass-loader/dist/cjs.js??ruleSet[1].rules[11].oneOf[1].use[3]!./node\_modules/sweetalert2/src/sweetalert2.scss > > 4:38:09 PM: success Building production JavaScript and CSS bundles - 74.037s > > 4:38:09 PM: warning [deprecated default-site-plugin] node.fs is deprecated. Please set “resolve.fallback.fs = false”. > > 4:38:37 PM: success Building HTML renderer - 28.105s > > 4:38:37 PM: success Execute page configs - 0.035s > > 4:38:37 PM: success Caching Webpack compilations - 0.000s > > 4:38:53 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/authorTemplate.js > > 4:38:53 PM: URL path: /blog/author/deniz-mustafa > > 4:38:53 PM: Context: { > > 4:38:53 PM: “dataPath”: “/content/posts/”, > > 4:38:53 PM: “slug”: “Deniz Mustafa” > > 4:38:53 PM: } > > 4:38:53 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/authorTemplate.js > > 4:38:53 PM: URL path: /blog/author/erin-grace-kelly > > 4:38:53 PM: Context: { > > 4:38:53 PM: “dataPath”: “/content/posts/”, > > 4:38:53 PM: “slug”: “Erin Grace Kelly” > > 4:38:53 PM: } > > 4:38:53 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/authorTemplate.js > > 4:38:53 PM: URL path: /blog/author/fuaad-aidarus > > 4:38:53 PM: Context: { > > 4:38:53 PM: “dataPath”: “/content/posts/”, > > 4:38:53 PM: “slug”: “Fuaad Aidarus” > > 4:38:53 PM: } > > 4:38:53 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/authorTemplate.js > > 4:38:53 PM: URL path: /blog/author/nazifa-alam > > 4:38:53 PM: Context: { > > 4:38:53 PM: “dataPath”: “/content/posts/”, > > 4:38:53 PM: “slug”: “Nazifa Alam” > > 4:38:53 PM: } > > 4:39:35 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/components/blog/index.js > > 4:39:35 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/components/blog/newsPage.js > > 4:39:35 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/components/home/index.js > > 4:39:35 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/components/layout/index.js > > 4:39:41 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/blogTemplate.js > > 4:39:41 PM: URL path: /blog/cyber-security-and-supply-chains > > 4:39:41 PM: Context: { > > 4:39:41 PM: “prefix”: “blog”, > > 4:39:41 PM: “previousSlug”: “What is Scareware?”, > > 4:39:41 PM: “nextSlug”: “Guidelines for ensuring secure provisioning and distribution of devices”, > > 4:39:41 PM: “slug”: "Cyber security and supply chains " > > 4:39:41 PM: } > > 4:39:41 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/blogTemplate.js > > 4:39:41 PM: URL path: /blog/guidelines-for-ensuring-secure-provisioning-and-distribution-of-devices > > 4:39:41 PM: Context: { > > 4:39:41 PM: “prefix”: “blog”, > > 4:39:41 PM: “previousSlug”: "Cyber security and supply chains ", > > 4:39:41 PM: “nextSlug”: “How a managed detection and response (MDR) platform can help keep your organization secure”, > > 4:39:41 PM: “slug”: “Guidelines for ensuring secure provisioning and distribution of devices” > > 4:39:41 PM: } > > 4:39:41 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/blogTemplate.js > > 4:39:41 PM: URL path: /blog/how-a-managed-detection-and-response-mdr-platform-can-help-keep-your-organization-secure > > 4:39:41 PM: Context: { > > 4:39:41 PM: “prefix”: “blog”, > > 4:39:41 PM: “previousSlug”: “Guidelines for ensuring secure provisioning and distribution of devices”, > > 4:39:41 PM: “nextSlug”: "E-skimming: as shopping moves online so does credit card skimming ", > > 4:39:41 PM: “slug”: “How a managed detection and response (MDR) platform can help keep your organization secure” > > 4:39:41 PM: } > > 4:39:41 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/blogTemplate.js > > 4:39:41 PM: URL path: /blog/e-skimming-as-shopping-moves-online-so-does-credit-card-skimming > > 4:39:41 PM: Context: { > > 4:39:41 PM: “prefix”: “blog”, > > 4:39:41 PM: “previousSlug”: “How a managed detection and response (MDR) platform can help keep your organization secure”, > > 4:39:41 PM: “nextSlug”: "What are FERPA, COPPA and HIPAA and why are they important? ", > > 4:39:41 PM: “slug”: "E-skimming: as shopping moves online so does credit card skimming " > > 4:39:41 PM: } > > 4:40:21 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/authorTemplate.js > > 4:40:21 PM: URL path: /news/author/reuben-soanes > > 4:40:21 PM: Context: { > > 4:40:21 PM: “dataPath”: “/content/news-posts/”, > > 4:40:21 PM: “slug”: “Reuben Soanes” > > 4:40:21 PM: } > > 4:40:21 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/authorTemplate.js > > 4:40:21 PM: URL path: /news/author/ryan-branagan > > 4:40:21 PM: Context: { > > 4:40:21 PM: “dataPath”: “/content/news-posts/”, > > 4:40:21 PM: “slug”: “Ryan Branagan” > > 4:40:21 PM: } > > 4:40:21 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/authorTemplate.js > > 4:40:21 PM: URL path: /news/author/william-moors > > 4:40:21 PM: Context: { > > 4:40:21 PM: “dataPath”: “/content/news-posts/”, > > 4:40:21 PM: “slug”: “William Moors” > > 4:40:21 PM: } > > 4:40:22 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/blogTemplate.js > > 4:40:22 PM: URL path: /blog/five-ways-to-protect-your-business-from-keylogging > > 4:40:22 PM: Context: { > > 4:40:22 PM: “prefix”: “blog”, > > 4:40:22 PM: “nextSlug”: “Types of hackers”, > > 4:40:22 PM: “slug”: “Five ways to protect your business from keylogging” > > 4:40:22 PM: } > > 4:40:51 PM: warning This query took more than 15s to run — which is unusually long and might indicate you’re querying too much or have some unoptimized code: > File path: /opt/build/repo/src/template/blogTemplate.js > > 4:40:51 PM: URL path: /blog/types-of-hackers > > 4:40:51 PM: Context: { > > 4:40:51 PM: “prefix”: “blog”, > > 4:40:51 PM: “previousSlug”: “Five ways to protect your business from keylogging”, > > 4:40:51 PM: “nextSlug”: “How to Recover From a Cyberattack”, > > 4:40:51 PM: “slug”: “Types of hackers” > > 4:40:51 PM: } > > 4:51:13 PM: success run queries in workers - 755.795s - 384/384 0.51/s > > 4:51:13 PM: success Running gatsby-plugin-sharp.IMAGE\_PROCESSING jobs - 864.779s - 742/742 0.86/s > > 4:51:13 PM: success Merge worker state - 0.388s > > 4:51:13 PM: success Rewriting compilation hashes - 0.001s > > 4:51:37 PM: success Writing page-data.json files to public directory - 23.447s - 379/379 16.16/s > > 4:51:51 PM: warning When server rendering, you must wrap your application in an to ensure consistent ids are generated between the client and server. > > 4:51:51 PM: success Building static HTML for pages - 14.060s - 379/379 26.96/s > > 4:51:51 PM: info [gatsby-plugin-netlify] Creating SSR redirects… > > 4:51:51 PM: info [gatsby-plugin-netlify] Created 0 SSR redirects… > > 4:51:51 PM: info [gatsby-plugin-netlify] No Netlify functions needed. Skipping… > > 4:51:51 PM: success onPostBuild - 0.308s > > 4:51:51 PM: > > 4:51:51 PM: Pages > > 4:51:51 PM: ┌ src/template/authorTemplate.js > > 4:51:51 PM: │ ├ /blog/author/deniz-mustafa > > 4:51:51 PM: │ └ …15 more pages available > > 4:51:51 PM: ├ src/template/blogTemplate.js > > 4:51:51 PM: │ ├ /blog/five-ways-to-protect-your-business-from-keylogging > > 4:51:51 PM: │ └ …324 more pages available > > 4:51:51 PM: ├ src/template/categoryTemplate.js > > 4:51:51 PM: │ ├ /blog/category/attack-surface-management > > 4:51:51 PM: │ └ …9 more pages available > > 4:51:51 PM: ├ src/template/industryTemplate.js > > 4:51:51 PM: │ ├ /education/ > > 4:51:51 PM: │ └ …5 more pages available > > 4:51:51 PM: ├ src/template/featuresTemplate.js > > 4:51:51 PM: │ ├ /alerts/ > > 4:51:51 PM: │ └ …5 more pages available > > 4:51:51 PM: ├ src/pages/404.js > > 4:51:51 PM: │ ├ /404/ > > 4:51:51 PM: │ └ /404.html > > 4:51:51 PM: ├ src/pages/about.js > > 4:51:51 PM: │ └ /about/ > > 4:51:51 PM: ├ src/pages/authors.js > > 4:51:51 PM: │ └ /authors/ > > 4:51:51 PM: ├ src/pages/blog.js > > 4:51:51 PM: │ └ /blog/ > > 4:51:51 PM: ├ src/pages/coming-soon.js > > 4:51:51 PM: │ └ /coming-soon/ > > 4:51:51 PM: ├ src/pages/contact.js > > 4:51:51 PM: │ └ /contact/ > > 4:51:51 PM: ├ src/pages/cookie-policy.js > > 4:51:51 PM: │ └ /cookie-policy/ > > 4:51:51 PM: ├ src/pages/index.js > > 4:51:51 PM: │ └ / > > 4:51:51 PM: ├ src/pages/news.js > > 4:51:51 PM: │ └ /news/ > > 4:51:51 PM: ├ src/pages/pricing.js > > 4:51:51 PM: │ └ /pricing/ > > 4:51:51 PM: ├ src/pages/privacy-policy.js > > 4:51:51 PM: │ └ /privacy-policy/ > > 4:51:51 PM: ├ src/pages/terms-of-use.js > > 4:51:51 PM: │ └ /terms-of-use/ > > 4:51:51 PM: ├ src/pages/thank-you.js > > 4:51:51 PM: │ └ /thank-you/ > > 4:51:51 PM: ├ src/pages/why-securiwiser.js > > 4:51:51 PM: │ └ /why-securiwiser/ > > 4:51:51 PM: └ src/pages/news/authors.js > > 4:51:51 PM: └ /news/authors/ > > 4:51:51 PM: ╭────────────────────────────────────────────────────────────────────╮ > > 4:51:51 PM: │ │ > > 4:51:51 PM: │ (SSG) Generated at build time │ > > 4:51:51 PM: │ D (DSG) Deferred static generation - page generated at runtime │ > > 4:51:51 PM: │ ∞ (SSR) Server-side renders at runtime (uses getServerData) │ > > 4:51:51 PM: │ λ (Function) Gatsby function │ > > 4:51:51 PM: │ │ > > 4:51:51 PM: ╰────────────────────────────────────────────────────────────────────╯ > > 4:51:51 PM: info Done building in 927.602246753 sec > > 4:51:51 PM: ​ > > 4:51:51 PM: (build.command completed in 15m 28.2s) > > 4:51:51 PM: ​ > > 4:51:51 PM: ──────────────────────────────────────────────────────────────── > > 4:51:51 PM: 3. netlify/plugin-gatsby (onBuild event) > > 4:51:51 PM: ──────────────────────────────────────────────────────────────── > > 4:51:51 PM: ​ > > 4:51:51 PM: Skipping Gatsby Functions and SSR/DSG support because gatsby-plugin-netlify reported that this site does not use them. > > 4:51:51 PM: If this is incorrect, remove the file “/opt/build/repo/.cache/.nf-skip-gatsby-functions” and try again. > > 4:51:51 PM: ​ > > 4:51:51 PM: ( netlify/plugin-gatsby onBuild completed in 18ms) > > 4:51:51 PM: ​ > > 4:51:51 PM: ──────────────────────────────────────────────────────────────── > > 4:51:51 PM: 4. netlify/plugin-gatsby (onPostBuild event) > > 4:51:51 PM: ──────────────────────────────────────────────────────────────── > > 4:51:51 PM: ​ > > 4:51:58 PM: Could not check zip size because /tmp/zisi-6224cebcb576c90008b958f6/\_\_api.zip does not exist > > 4:51:58 PM: Could not check zip size because /tmp/zisi-6224cebcb576c90008b958f6/\_\_dsg.zip does not exist > > 4:51:58 PM: Could not check zip size because /tmp/zisi-6224cebcb576c90008b958f6/\_\_ssr.zip does not exist > > 4:51:58 PM: ​ > > 4:51:58 PM: ( netlify/plugin-gatsby onPostBuild completed in 6.5s) > > 4:51:58 PM: ​ > > 4:51:58 PM: ──────────────────────────────────────────────────────────────── > > 4:51:58 PM: 5. Deploy site > > 4:51:58 PM: ──────────────────────────────────────────────────────────────── > > 4:51:58 PM: ​ > > 4:51:58 PM: Starting to deploy site from ‘public’ > > 4:52:01 PM: Creating deploy tree asynchronously > > 4:52:04 PM: 493 new files to upload > > 4:52:04 PM: 0 new functions to upload > > 4:52:54 PM: Site deploy was successfully initiated > > 4:52:54 PM: ​ > > 4:52:54 PM: (Deploy site completed in 56.4s) > > 4:52:55 PM: ​ > > 4:52:55 PM: ──────────────────────────────────────────────────────────────── > > 4:52:55 PM: Netlify Build Complete > > 4:52:55 PM: ──────────────────────────────────────────────────────────────── > > 4:52:55 PM: ​ > > 4:52:55 PM: (Netlify Build completed in 16m 46.8s) > > 4:52:55 PM: Execution timed out after 18m8.43859981s > > 4:52:55 PM: Error running command: Command did not finish within the time limit > > 4:52:55 PM: Creating deploy upload records > > 4:52:56 PM: Failing build: Failed to build site > > 4:52:56 PM: Failed during stage ‘building site’: Command did not finish within the time limit > > 4:52:56 PM: Finished processing build request in 18m16.010323949s > > 4:54:54 PM: Starting post processing > > 4:54:54 PM: Post processing - HTML > > 4:54:57 PM: Processing form - contact > > 4:54:57 PM: Detected form fields: > > 4:54:57 PM: - contact > > 4:54:57 PM: - firstname > > 4:54:57 PM: - lastname > > 4:54:57 PM: - email > > 4:54:58 PM: - companyname > > 4:54:58 PM: - phone > > 4:54:58 PM: - query > > 4:54:58 PM: - message > > 4:56:17 PM: Post processing - header rules > > 4:56:17 PM: Post processing - redirect rules > > 4:56:18 PM: Post processing done > > 4:56:21 PM: Site is live ✨ **Gatsby info:** System: ``` OS: Windows 10 10.0.22000 CPU: (8) x64 Intel(R) Core(TM) i7-1065G7 CPU 1.30GHz ``` Binaries: ``` Node: 16.14.0 - C:\Program Files\nodejs\node.EXE npm: 8.5.3 - ~\AppData\Roaming\npm\npm.CMD ``` Languages: ``` Python: 2.7.15 ``` Browsers: ``` Edge: Spartan (44.22000.120.0), Chromium (99.0.1150.30) ``` npmPackages: ``` gatsby: ^4.9.1 => 4.9.1 gatsby-image: ^3.11.0 => 3.11.0 gatsby-plugin-advanced-sitemap: ^2.0.0 => 2.0.0 gatsby-plugin-canonical-urls: ^4.2.0 => 4.9.0 gatsby-plugin-facebook-pixel: ^1.0.8 => 1.0.8 gatsby-plugin-force-trailing-slashes: ^1.0.5 => 1.0.6 gatsby-plugin-gdpr-cookies: ^2.0.8 => 2.0.8 gatsby-plugin-google-analytics: ^4.2.0 => 4.9.0 gatsby-plugin-google-gtag: ^4.2.0 => 4.9.0 gatsby-plugin-image: ^2.1.1 => 2.9.0 gatsby-plugin-mailchimp: ^5.2.2 => 5.2.2 gatsby-plugin-manifest: ^4.1.2 => 4.9.0 gatsby-plugin-mdx: ^3.2.0 => 3.9.0 gatsby-plugin-netlify: ^4.1.0 => 4.1.0 gatsby-plugin-netlify-cms: ^6.2.0 => 6.9.0 gatsby-plugin-preact: ^6.9.0 => 6.9.0 gatsby-plugin-preload-fonts: ^3.4.0 => 3.9.0 gatsby-plugin-react-helmet: ^5.1.0 => 5.9.0 gatsby-plugin-robots-txt: ^1.6.14 => 1.7.0 gatsby-plugin-sass: ^5.1.1 => 5.9.0 gatsby-plugin-sharp: ^4.1.2 => 4.9.0 gatsby-remark-images: ^6.2.0 => 6.9.0 gatsby-source-filesystem: ^4.1.1 => 4.9.0 gatsby-transformer-json: ^4.2.0 => 4.9.0 gatsby-transformer-remark: ^5.2.0 => 5.9.0 gatsby-transformer-sharp: ^4.1.0 => 4.9.0 ``` npmGlobalPackages: ``` gatsby-cli: 4.9.0 ``` ---
**Author:** ![hrishikesh](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hrishikesh/32/74607_2.png) [@hrishikesh](https://answers.netlify.com/u/hrishikesh)\ **Post date:** [August 7, 2022, 12:59pm UTC](https://answers.netlify.com/t/gatsby-build-takes-too-long-went-from-5m-to-30m-execution-timed-out-after-18m-still-builds/52971/4 "2022-08-07T12:59:33Z")
Hey @aburuqayyah, Sorry about this one. As it appears, due to some problem with our issue tracking, we never saw this thread. Do you still need help with this?