Home
Support Forums

Issues with build process

in my logs, i’m no longer getting

your site is live!

on the deploys page, my build process is complete

on the Site Overview, my production deploy is Processing

however the site itself never updates with the latest copy.

I’ve read through [Support Guide] Debugging Netlify site builds

https://app.netlify.com/teams/contact-th5sdwi/builds/60dd5e1eb83cb900088d8c66

4:18:07 PM: Build ready to start
4:18:09 PM: build-image version: 2cee85eb7f808bf3b6e87378c5307f9411f0a332
4:18:09 PM: build-image tag: v3.8.0
4:18:09 PM: buildbot version: 3a7a1c278c6c7edcd494fc2a7498f3b49c5193d6
4:18:09 PM: Fetching cached dependencies
4:18:09 PM: Starting to download cache of 304.5MB
4:18:10 PM: Finished downloading cache in 1.381522842s
4:18:10 PM: Starting to extract cache
4:18:21 PM: Finished extracting cache in 10.527857686s
4:18:21 PM: Finished fetching cache in 11.981856265s
4:18:21 PM: Starting to prepare the repo for build
4:18:21 PM: Preparing Git Reference refs/heads/main
4:18:25 PM: Parsing package.json dependencies
4:18:25 PM: Different build dir detected, going to use the one specified in the Netlify configuration file: '' versus '/' in the Netlify UI
4:18:26 PM: Starting build script
4:18:26 PM: Installing dependencies
4:18:26 PM: Python version set to 2.7
4:18:26 PM: Started restoring cached node version
4:18:29 PM: Finished restoring cached node version
4:18:30 PM: v12.18.0 is already installed.
4:18:30 PM: Now using node v12.18.0 (npm v6.14.4)
4:18:30 PM: Started restoring cached build plugins
4:18:30 PM: Finished restoring cached build plugins
4:18:30 PM: Attempting ruby version 2.7.1, read from environment
4:18:31 PM: Started restoring cached ruby version
4:18:31 PM: Finished restoring cached ruby version
4:18:33 PM: Using ruby version 2.7.1
4:18:33 PM: Using PHP version 5.6
4:18:33 PM: Started restoring cached yarn cache
4:18:33 PM: Finished restoring cached yarn cache
4:18:34 PM: Yarn workspaces detected
4:18:34 PM: Started restoring workspace packages/blog/gatsby-blog-core node modules
4:18:34 PM: Finished restoring workspace packages/blog/gatsby-blog-core node modules
4:18:34 PM: Started restoring workspace packages/plugins/gatsby-plugin-utility-directives node modules
4:18:34 PM: Finished restoring workspace packages/plugins/gatsby-plugin-utility-directives node modules
4:18:34 PM: Started restoring workspace site node modules
4:18:34 PM: Finished restoring workspace site node modules
4:18:34 PM: Started restoring workspace root node modules
4:18:34 PM: Finished restoring workspace root node modules
4:18:34 PM: Installing NPM modules using Yarn version 1.22.4
4:18:35 PM: yarn install v1.22.4
4:18:35 PM: [1/5] Validating package.json...
4:18:35 PM: [2/5] Resolving packages...
4:18:36 PM: success Already up-to-date.
4:18:36 PM: Done in 1.30s.
4:18:36 PM: NPM modules installed using Yarn
4:18:36 PM: Started restoring cached go cache
4:18:36 PM: Finished restoring cached go cache
4:18:36 PM: go version go1.14.4 linux/amd64
4:18:36 PM: go version go1.14.4 linux/amd64
4:18:36 PM: Installing missing commands
4:18:36 PM: Verify run directory
4:18:37 PM: ​
4:18:37 PM: ────────────────────────────────────────────────────────────────
4:18:37 PM:   Netlify Build                                                 
4:18:37 PM: ────────────────────────────────────────────────────────────────
4:18:37 PM: ​
4:18:37 PM: ❯ Version
4:18:37 PM:   @netlify/build 12.20.0
4:18:37 PM: ​
4:18:37 PM: ❯ Flags
4:18:37 PM:   deployId: 60dd5e1eb83cb900088d8c66
4:18:37 PM: ​
4:18:37 PM: ❯ Current directory
4:18:37 PM:   /opt/build/repo
4:18:37 PM: ​
4:18:37 PM: ❯ Config file
4:18:37 PM:   /opt/build/repo/netlify.toml
4:18:37 PM: ​
4:18:37 PM: ❯ Context
4:18:37 PM:   production
4:18:37 PM: ​
4:18:37 PM: ❯ Loading plugins
4:18:37 PM:    - @netlify/plugin-gatsby@1.0.3 from netlify.toml and package.json
4:18:37 PM: ​
4:18:37 PM: ────────────────────────────────────────────────────────────────
4:18:37 PM:   1. onPreBuild command from @netlify/plugin-gatsby             
4:18:37 PM: ────────────────────────────────────────────────────────────────
4:18:37 PM: ​
4:18:40 PM: Found a Gatsby cache. We’re about to go FAST. ⚡️
4:18:40 PM: Add `gatsby-plugin-netlify` to `gatsby-config.js` if you would like to support Gatsby redirects. 🎉
4:18:40 PM: ​
4:18:40 PM: (@netlify/plugin-gatsby onPreBuild completed in 2.9s)
4:18:40 PM: ​
4:18:40 PM: ────────────────────────────────────────────────────────────────
4:18:40 PM:   2. build.command from netlify.toml                            
4:18:40 PM: ────────────────────────────────────────────────────────────────
4:18:40 PM: ​
4:18:40 PM: $ cd site && yarn build
4:18:41 PM: yarn run v1.22.4
4:18:41 PM: $ gatsby build --log-pages
4:18:43 PM: info The following flags are active:
4:18:43 PM: - PRESERVE_WEBPACK_CACHE · (Umbrella Issue (https://gatsby.dev/cache-clearing-feedback)) · Use webpack's persistent caching and don't delete webpack's cache when changing gatsby-node.js & gatsby-config.js files.
4:18:43 PM: There are 2 other flags available that you might be interested in:
4:18:43 PM: - PRESERVE_FILE_DOWNLOAD_CACHE · (Umbrella Issue (https://gatsby.dev/cache-clearing-feedback)) · Don't delete the downloaded files cache when changing gatsby-node.js & gatsby-config.js files.
4:18:43 PM: - PARALLEL_SOURCING · EXPERIMENTAL · (Umbrella Issue (https://gatsby.dev/parallel-sourcing-feedback)) · 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:18:44 PM: success open and validate gatsby-configs - 0.248s
4:18:45 PM: warning Plugin gatsby-plugin-emotion is not compatible with your gatsby version 3.7.1 - It requires gatsby@^2.0.0
4:18:45 PM: warning Plugin gatsby-plugin-emotion is not compatible with your gatsby version 3.7.1 - It requires gatsby@^2.0.0
4:18:45 PM: success load plugins - 1.492s
4:18:45 PM: success onPreInit - 0.098s
4:18:45 PM: info One or more of your plugins have changed since the last time you ran Gatsby. As
4:18:45 PM: a precaution, we're deleting your site's cache to ensure there's no stale data.success initialize cache - 0.092s
4:18:45 PM: success copy gatsby files - 0.099s
4:18:46 PM: success Compiling Gatsby Functions - 0.440s
4:18:46 PM: success onPreBootstrap - 0.468s
4:18:46 PM: success createSchemaCustomization - 0.184s
4:19:23 PM: success Checking for changed pages - 0.000s
4:19:23 PM: success source and transform nodes - 37.362s
4:19:25 PM: success building schema - 1.046s
4:19:25 PM: success createPages - 0.329s
4:19:25 PM: success createPagesStatefully - 0.183s
4:19:25 PM: info Total nodes: 1855, SitePage nodes: 140 (use --verbose for breakdown)
4:19:25 PM: success Checking for changed pages - 0.000s
4:19:25 PM: success Cleaning up stale page-data - 0.007s
4:19:25 PM: success update schema - 0.165s
4:19:25 PM: success onPreExtractQueries - 0.000s
4:19:28 PM: success extract queries from components - 2.315s
4:19:28 PM: success write out redirect data - 0.001s
4:19:28 PM: success onPostBootstrap - 0.062s
4:19:28 PM: info bootstrap finished - 46.982s
4:19:28 PM: warning GraphQL Resolver got called without "info" argument. This might cause unexpected errors.
4:19:28 PM: It's likely that this has happened in a schemaCustomization with manually invoked resolver. If manually invoking resolvers, it's best to invoke them as follows:
4:19:28 PM:   resolve(parent, args, context, info)
4:19:41 PM: success run static queries - 12.937s - 11/11 0.85/s
4:19:56 PM: warning Query takes too long:
4:19:56 PM: File path: /opt/build/repo/packages/blog/gatsby-blog-core/src/templates/post.js

4:19:56 PM: warning Query takes too long:
4:19:56 PM: File path: /opt/build/repo/packages/blog/gatsby-blog-core/src/templates/post.js

4:19:56 PM: warning Query takes too long:
4:19:56 PM: File path: /opt/build/repo/packages/blog/gatsby-blog-core/src/templates/post.js

4:23:08 PM: warning Query takes too long:
4:23:08 PM: File path: /opt/build/repo/packages/blog/gatsby-blog-core/src/templates/post.js

4:23:09 PM: warning Query takes too long:
4:23:09 PM: File path: /opt/build/repo/packages/blog/gatsby-blog-core/src/templates/post.js

4:23:11 PM: warning Query takes too long:
4:23:11 PM: File path: /opt/build/repo/packages/blog/gatsby-blog-core/src/templates/post.js

4:23:13 PM: warning Query takes too long:
4:23:13 PM: File path: /opt/build/repo/packages/blog/gatsby-blog-core/src/templates/post.js

4:23:24 PM: error [BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
4:23:30 PM: error [BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
4:23:34 PM: error [BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
4:24:13 PM: success run page queries - 272.564s - 140/140 0.51/s
4:24:13 PM: success write out requires - 0.008s
4:24:16 PM: success Building production JavaScript and CSS bundles - 3.121s
4:24:16 PM: success Caching JavaScript and CSS webpack compilation - 0.005s
4:24:16 PM: success Rewriting compilation hashes - 0.003s
4:24:23 PM: success Building HTML renderer - 6.142s
4:24:24 PM: success Caching HTML renderer compilation - 1.230s
4:24:33 PM: success Building static HTML for pages - 10.731s - 140/140 13.05/s
4:24:40 PM: success index to Algolia - 6.763s - Done!
4:24:40 PM: success onPostBuild - 6.807s
4:24:40 PM: info Done building in 359.764153392 sec
4:24:41 PM: Done in 360.36s.
4:24:41 PM: ​
4:24:41 PM: (build.command completed in 6m 0.6s)
4:24:41 PM: ​
4:24:41 PM: ────────────────────────────────────────────────────────────────
4:24:41 PM:   3. onBuild command from @netlify/plugin-gatsby                
4:24:41 PM: ────────────────────────────────────────────────────────────────
4:24:41 PM: ​
4:24:41 PM: ​
4:24:41 PM: (@netlify/plugin-gatsby onBuild completed in 25ms)
4:24:41 PM: ​
4:24:41 PM: ────────────────────────────────────────────────────────────────
4:24:41 PM:   4. Functions bundling                                         
4:24:41 PM: ────────────────────────────────────────────────────────────────
4:24:41 PM: ​
4:24:42 PM: Packaging Functions from netlify/functions directory:
4:24:42 PM:  - gatsby/gatsby.js
4:24:42 PM: ​
4:24:43 PM: ​
4:24:43 PM: (Functions bundling completed in 2.1s)
4:24:43 PM: ​
4:24:43 PM: ────────────────────────────────────────────────────────────────
4:24:43 PM:   5. onPostBuild command from @netlify/plugin-gatsby            
4:24:43 PM: ────────────────────────────────────────────────────────────────
4:24:43 PM: ​
4:24:46 PM: ​
4:24:46 PM: (@netlify/plugin-gatsby onPostBuild completed in 3.1s)
4:24:46 PM: ​
4:24:46 PM: ────────────────────────────────────────────────────────────────
4:24:46 PM:   6. Deploy site                                                
4:24:46 PM: ────────────────────────────────────────────────────────────────
4:24:46 PM: ​
4:24:46 PM: Starting to deploy site from 'site/public'
4:24:46 PM: Creating deploy tree asynchronously
4:24:46 PM: Creating deploy upload records
4:24:49 PM: 50 new files to upload
4:24:49 PM: 0 new functions to upload
4:24:50 PM: Site deploy was successfully initiated
4:24:50 PM: ​
4:24:50 PM: (Deploy site completed in 4.3s)
4:24:51 PM: ​
4:24:51 PM: ────────────────────────────────────────────────────────────────
4:24:51 PM:   Netlify Build Complete                                        
4:24:51 PM: ────────────────────────────────────────────────────────────────
4:24:51 PM: ​
4:24:51 PM: (Netlify Build completed in 6m 13.6s)
4:24:51 PM: Caching artifacts
4:24:51 PM: Started saving workspace packages/blog/gatsby-blog-core node modules
4:24:51 PM: Finished saving workspace packages/blog/gatsby-blog-core node modules
4:24:51 PM: Started saving workspace packages/plugins/gatsby-plugin-utility-directives node modules
4:24:51 PM: Finished saving workspace packages/plugins/gatsby-plugin-utility-directives node modules
4:24:51 PM: Started saving workspace site node modules
4:24:51 PM: Finished saving workspace site node modules
4:24:51 PM: Started saving workspace root node modules
4:24:51 PM: Finished saving workspace root node modules
4:24:51 PM: Started saving build plugins
4:24:51 PM: Finished saving build plugins
4:24:51 PM: Started saving yarn cache
4:24:51 PM: Finished saving yarn cache
4:24:51 PM: Started saving pip cache
4:24:51 PM: Finished saving pip cache
4:24:51 PM: Started saving emacs cask dependencies
4:24:51 PM: Finished saving emacs cask dependencies
4:24:51 PM: Started saving maven dependencies
4:24:51 PM: Finished saving maven dependencies
4:24:51 PM: Started saving boot dependencies
4:24:51 PM: Finished saving boot dependencies
4:24:51 PM: Started saving rust rustup cache
4:24:51 PM: Finished saving rust rustup cache
4:24:51 PM: Started saving go dependencies
4:24:51 PM: Finished saving go dependencies
4:24:51 PM: Build script success
4:24:54 PM: Starting post processing
4:24:54 PM: Skipping HTML post processing
4:24:54 PM: Post processing - header rules
4:24:54 PM: Post processing - redirect rules
4:25:34 PM: Finished processing build request in 7m25.801540873s

Hey Robert,

It looks like the build is either hanging, or it isn’t successfully processing during the post-processing phase.

You will want to check out this support guide to learn more about builds which are hanging. There’s a few measures you can take to understand what part of the build may not be terminating correctly.

Additionally, I have increased the default 5 minute time limit for processing phase of the build to 15 minutes.

Please do take some time to try and identify any long running background processes. Feel free to report back with any developments!

It looks as through my _redirects file with 1000+ lines of redirects was causing the build to fail, @Scott . Temporary solution right now, i’ve cut out half of them, but i’ll reinvestigate this in the coming week.

Interesting! Usually, it’s 10k+ redirects which would cause a problem but we do have a character limit on the redirect rules, once parsed.

If possible, you should try and make use of placeholders and common denotations to reduce the number of redirects you have. Not only will large files make your deploys a little less resilient but it adds latency to every request!