Building went from working to failing for seemingly no reason

Support
1

Hello,

we have a problem with building our Site internationalestiftung.netlify.app at the moment.
The last working build was on 17.01.2025. On 03.02.2025 we added some content to Wordpress and triggered a rebuild. Ever since we didn’t manage to build the site successfully.

Sadly the error message in the log isn’t very helpful as it’s just “error UNHANDLED EXCEPTION write EPIPE” which could be triggered by many different things. It would be nice if we (or you) could take a look at the full logs to spot the issue.

Best Regards

2

@michaela Debugging your build process is outside of Netlify’s ‘Scope of Support’:
https://www.netlify.com/support-scope/

Base functionality of Netlify’s build and deploy pipeline is supported, but we cannot help you debug any source code used either during build or after deployment.

Since you mention that your site is connected to WordPress and the error started occurring after you changed content, it’s likely that changed content has caused the issue.

This thread is unrelated to your precise issue, (as they’re running different code), but serves as a good recent example where someone else found that ‘content can cause an error’:
https://answers.netlify.com/t/sudden-build-failure/139631/2

3

We removed the Blogpost in Question but the build still fails with the same error message. I don’t see how we could solve this without access to proper logs.

4

@michaela Netlify are providing ‘proper logs’, as they display ‘what your build outputs’.

Have you tried running the same build command locally to see if it encounters the error there?

You’ve not yet mentioned what system your site is built with.
Is it Next, Nuxt, Gatsby, Vite, React?

5

We’re using Gatsby as a build system. What I meant with proper logs is an actually helpful error message optimally with a trace to see the cause of the error. Running the project locally is a bit of a pain because of WordPress. Is there really no way like a flag or something to set the logging level to debug or otherwise get our hands at debug level logs?

6

Hi @michaela,

Thanks for reaching out! Sorry to hear about the issue.

Checking the latest build failure, I’m seeing this error:

error UNHANDLED EXCEPTION write EPIPE

I see you’re using Gatsby version 4.9.1. I found this thread that may help:

Looks like the solution is to upgrade to version 4.13 mentioned here in that thread. Could you give that a try to see if it resolves the issue?

7

@michaela You should try @Melvin’s suggestion, but to answer your question…

This is the responsibility of the build system that you’re working with.

Taking a quick look at Gatsby’s documentation, you could try their ‘verbose logs’:
https://www.gatsbyjs.com/docs/reference/cloud/build-logs/#verbose-logs