Error during build - Failed to retrieve metadata from image ... Input file is missing

Description

I have Gatsby project connected with WordPress. It’s hosted on Vercel. When triggering build from WP (via webhook) I’m getting following error:

error Failed to retrieve metadata from image /vercel/7c48990a/.cache/caches/gatsby-source-filesystem/4bea188c5eff0f6506668c8acc73697b/img_1-1_sistable.jpg Input file is missing

It’s weird that error occurs in about 50% of builds triggered. So when build ends with error - I’m able to trigger another build from WP (not changing anything) and it build successfully.

Steps to reproduce

I can’t share entire code as it’s business project for a client, but let me know if anything more would be helpful for you.

The scenario for reproduce a bug is:

• make any changes within WordPress (plugin JAMstack Deployments is set up to create POST request to Vercel Build Hook URL)
• login to Vercel and see Deployments tab (sometimes there’s error, sometimes not)

Expected result

Successful build

Actual result

Following error:

error Failed to retrieve metadata from image /vercel/7c48990a/.cache/caches/gatsby-source-filesystem/4bea188c5eff0f6506668c8acc73697b/img_1-1_sistable.jpg Input file is missing

Environment

  System:
    OS: macOS Mojave 10.14.6
    CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.5.0 - ~/.nvm/versions/node/v14.5.0/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.14.5 - ~/.nvm/versions/node/v14.5.0/bin/npm
  Languages:
    Python: 2.7.10 - /usr/bin/python
  Browsers:
    Chrome: 85.0.4183.102
    Edge: 85.0.564.51
    Firefox: 77.0.1
    Safari: 13.1.2
  npmPackages:
    gatsby: ^2.23.10 => 2.23.10
    gatsby-background-image: ^1.1.1 => 1.1.1
    gatsby-image: ^2.4.8 => 2.4.8
    gatsby-plugin-favicon: ^3.1.6 => 3.1.6
    gatsby-plugin-load-script: ^1.1.0 => 1.1.0
    gatsby-plugin-manifest: ^2.4.13 => 2.4.13
    gatsby-plugin-offline: ^3.2.12 => 3.2.12
    gatsby-plugin-react-helmet: ^3.3.5 => 3.3.5
    gatsby-plugin-sass: ^2.3.6 => 2.3.6
    gatsby-plugin-sharp: ^2.6.13 => 2.6.13
    gatsby-plugin-sitemap: ^2.4.7 => 2.4.7
    gatsby-plugin-web-font-loader: ^1.0.4 => 1.0.4
    gatsby-source-filesystem: ^2.3.13 => 2.3.13
    gatsby-source-wordpress: ^3.3.15 => 3.3.15
    gatsby-transformer-sharp: ^2.5.6 => 2.5.6
  npmGlobalPackages:
    gatsby-cli: 2.12.95

[runemadsen]

I’m running into the same issue in a GitHub action. It was the first time it ran on the machine, so there shouldn’t be any caching issues.

[leevi978]

Hello! I am getting this same error when building on Gatsby Cloud, but the console does not allow me to change the build command. Can this issue please be re-opened so that the developers may work on a fix?