Custom Types API - ETIMEDOUT failing build for number of sites

Developing with Prismic
1

Hi Prismic, a number of our client's Gatsby builds are failing due to the below error:

FetchError: request to https://customtypes.prismic.io/customtypes/ failed, reason: connect ETIMEDOUT

Seeing this on 6 sites, all using the V5 version of the gatsby-source-prismic plugin, the customTypesApiToken option and hosted on Gatsby Cloud. Is the API down and can you look into it as a matter of urgency as we're unable to push updates to their production sites? :pray:

Full error attached below:

13:37:38 PM:
ERROR "gatsby-source-prismic" threw an error while running the createSchemaCustomization lifecycle:

13:37:38 PM:
request to https://customtypes.prismic.io/customtypes/ failed, reason: connect ETIMEDOUT 13.249.87.21:443

13:37:38 PM:
  FetchError: request to https://customtypes.prismic.io/customtypes/ failed, rea  son: connect ETIMEDOUT 13.249.87.21:443

13:37:38 PM:
  - index.js:1483 ClientRequest.

13:37:38 PM:
    internal/streams/destroy.js:106:8

13:37:38 PM:
    [www]/[node-fetch]/lib/index.js:1483:11

13:37:38 PM:
  - destroy.js:106 emitErrorNT

13:37:38 PM:
  - destroy.js:74 emitErrorCloseNT

13:37:38 PM:
    internal/streams/destroy.js:74:3

13:37:38 PM:
    internal/process/task_queues.js:82:21

13:37:38 PM:
  - task_queues.js:82 processTicksAndRejections

13:37:43 PM:
ERROR Worker exited before finishing task

13:37:43 PM:
  Error: Worker exited before finishing task

13:37:43 PM:
  - index.js:112 ChildProcess.

13:37:43 PM:
  - child_process.js:282 Process.ChildProcess._handle.onexit

13:37:43 PM:
    [www]/[gatsby-worker]/dist/index.js:112:45

13:37:43 PM:
    internal/child_process.js:282:12
3

Hello @hey_botanic

Thanks for reaching out to us.

Does the build work well before? If so, It might be that you need to clear the cache of your project. Clear the cache, and re-build your project.

Let me know if it doesn't help.

Thanks,
Priyanka