# Gatsby-source-prismic stopped working

**URL:** <https://community.prismic.io/t/gatsby-source-prismic-stopped-working/8794>\
**Category:** Developing with Prismic\
**Tags:** gatsby\
**Created:** [January 25, 2022, 11:35pm UTC](https://community.prismic.io/t/gatsby-source-prismic-stopped-working/8794 "2022-01-25T23:35:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![blanchard](https://avatars.discourse-cdn.com/v4/letter/b/c5a1d2/32.png) [@blanchard](https://community.prismic.io/u/blanchard)\
**Post date:** [January 25, 2022, 11:35pm UTC](https://community.prismic.io/t/gatsby-source-prismic-stopped-working/8794/1 "2022-01-25T23:35:09Z")

</div>

My prismic + gatsby website is suddenly failing to build on local, with the following error:

Plugin gatsby-source-prismic returned an error request to [https://mascot.prismic.io/api/v2?access\_token=](https://mascot.prismic.io/api/v2?access_token=) $TOKEN\_GOES\_HERE failed, reason: getaddrinfo ENOTFOUND [mascot.prismic.io](http://mascot.prismic.io)

Clicking the link with the access\_token included pulls up the content explorer interface as expected.

What's hard to understand is why this stopped working suddenly. I haven't changed the codebase or upgraded any packages or even done a major macOS update (currently on 11.6 Big Sur). Deploys on Netlify are continuing to work as well.

---

<div class="post-metadata">

**Author:** ![Fares](https://avatars.discourse-cdn.com/v4/letter/f/71e660/32.png) [@Fares](https://community.prismic.io/u/Fares)\
**Post date:** [January 26, 2022, 5:18pm UTC](https://community.prismic.io/t/gatsby-source-prismic-stopped-working/8794/4 "2022-01-26T17:18:58Z")

</div>

Hi Chris,

Welcome to the Prismic community,  
As you might know when you build your project locally. Gatsby tries to fetch your data from Prismic, and there are a few cases where it might fail in case of corrupted Gatsby cache that is using an old Prismic API Ref or some time-outs.

In your case, I would favor the cache scenario, and to solve this, can you try to clean your Gatsby cache such as [`gatsby clean`](https://www.gatsbyjs.com/docs/reference/gatsby-cli/#clean)

Please let us know if that doesn't solve the issue to try to investigate further,  
Fares