Query execution error. Link to entry 'xxxxx' on field 'xxxx' within type 'xxxxx' cannot be resolved

[simonbetton]

Hi everyone!

I am using the gatsby-source-graphql package to pull data from the Contentful GraphQL API. When I make a request to the Contentful GraphQL API to retrieve published data, I get an error response for unpublished/drafted content being missing. Contentful intentionally output this GraphQL error and say how the error is handled is up to the application. Fair enough.

The error I get:

{
  "errors": [
    {
      "message": "Query execution error. Link to entry 'xxxxxxxxxxxxxxxxxx' on field 'xxxxx' within type 'xxxxxx' cannot be resolved",
      "locations": [
        {
          "line": 7,
          "column": 11
        }
      ],
      "path": [
        "contentful",
        "articleCollection",
        "items",
        0,
        "creditsCollection",
        "items",
        0
      ],
      "extensions": {
        "contentful": {
          "code": "UNRESOLVABLE_LINK",
          "requestId": "xxxxxxxxxxxxxxxxx",
          "details": {
            "type": "xxxxxx",
            "field": "xxxxxx",
            "linkType": "Entry",
            "linkId": "xxxxxxxxxxxxxxxxxx"
          }
        }
      },
      "stack": [
        "GraphQLError: Query execution error. Link to entry 'xxxxxxxxxxxxxxxxxx' on field 'xxxxxxxx' within type 'xxxxxxxx' cannot be resolved",
        "    at Object.relocatedError (/...xxxx/dist/utils/src/errors.js:4:12)",
        "    at handleNull (/...xxxx/node_modules/gatsby-source-graphql/dist/delegate/src/results/handleNull.js:11:43)",
        "    at handleListMember (/...xxxx/node_modules/gatsby-source-graphql/dist/delegate/src/results/handleList.js:11:16)",
        "    at /...xxxx/node_modules/gatsby-source-graphql/dist/delegate/src/results/handleList.js:7:44",
        "    at Array.map (<anonymous>)",
        "    at handleList (/...xxxx/node_modules/gatsby-source-graphql/dist/delegate/src/results/handleList.js:7:17)",
        "    at handleResult (/...xxxx/node_modules/gatsby-source-graphql/dist/delegate/src/results/handleResult.js:17:16)",
        "    at resolver (/...xxxx/node_modules/gatsby-source-graphql/dist/delegate/src/defaultMergedResolver.js:24:12)",
        "    at resolver (/...xxxx/node_modules/gatsby/src/schema/resolvers.ts:518:14)",
        "    at wrappedTracingResolver (/...xxxx/node_modules/gatsby/src/schema/resolvers.ts:518:14)",
        "    at resolveFieldValueOrError (/...xxxx/node_modules/graphql/execution/execute.js:467:18)",
        "    at resolveField (/...xxxx/node_modules/graphql/execution/execute.js:434:16)",
        "    at executeFields (/...xxxx/node_modules/graphql/execution/execute.js:275:18)",
        "    at collectAndExecuteSubfields (/...xxxx/node_modules/graphql/execution/execute.js:713:10)",
        "    at completeObjectValue (/...xxxx/node_modules/graphql/execution/execute.js:703:10)",
        "    at completeValue (/...xxxx/node_modules/graphql/execution/execute.js:591:12)"
      ]
    },
  ]
}

In Next.js there's Apollo and can configure your errorPolicy.

This error being output is causing a production build failure. It functions fine in develop.

Any ideas on how to resolve this issue?

[vladar]

Hey 👋

gatsby-source-graphql allows you to set a custom fetch implementation or if you prefer apollo - a custom apollo link via createLink option. You can handle this error there if you need to. See docs: https://www.gatsbyjs.com/plugins/gatsby-source-graphql/?=gatsby-source-graphql#how-to-use

Also, it is not entirely clear how exactly gatsby build fails for you and what behavior you expect in this case?

[simonbetton]

Hey mate, thanks for that.

I did take a look at that but createLink didn't look like I could use apollo-link-error to catch these errors. I may be wrong. I haven't been able to find any working examples of this. Have you?

The issue with the build seems to be purely based on there being an error object in the GraphQL response. Even though the response is http 200 response code.

[vladar]

I think createLink supports any apollo link, including one with apollo-link-error in the chain. Can you clarify a bit what did you try and what exactly didn't work for you?

Also as I mentioned you can just pass custom fetch implementation - and just console.log your response - and I think this is even easier to do than using links. Have you tried that?

[vladar]

Did you figure it out?

[simonbetton]

Sorry, yes, I did "kinda" resolved it. Here is my code. Looks like the repo has been updated since then and has better documentation around it..

{
  resolve: "gatsby-source-graphql",
  options: {
    typeName: "Contentful",
    fieldName: "contentful",
    createLink: () => {
      const httpLink = createHttpLink({
        uri: `...`,
        headers: {
          Authorization: `Bearer ...`,
        },
        fetch,
      });
      const errorLink = onError(({ response, graphQLErrors, networkError }) => {
        if (graphQLErrors) {
          graphQLErrors.forEach((err, key) => {
            switch (err.extensions.contentful.code) {
              case "UNRESOLVABLE_LINK":
                response.errors[key] = null;
            }
          });

          if (response && response.errors) {
            response.errors = response.errors.filter((el) => el != null) ?? null;
          }
        }

        if (networkError) console.log(`[Network error]: ${networkError}`);
      });
      return errorLink.concat(httpLink);
    },
  },
},

[simonbetton]

Bump