GraphQL error: Evaluation of custom field failed because external request returned an error

This similar problem happens to me, I don’t know if I already have an idea how to eliminate the error. Since I read the message there is talk of a package that was removed, but I don’t have this same package in use. Or how to check if it is being used? (This error is sometimes triggered, not all the time).

​⁠{“graphQLErrors”:{“message”:“GraphQL error: Evaluation of custom field failed because external request returned an error: Post “​⁠[http://router.fission.svc.cluster.local:80/cluster/0x2316753/0/graphql-worker](http://router.fission.svc.cluster.local/cluster/0x2316753/0/graphql-worker)​⁠”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) for field: ​⁠deliveryTAT​⁠ within type: Order.”}

Have you checked if the external call is reachable? with cURL or postman.

Yes, the problem happens sometimes, it is the doubt that I have. It is not a frequent error, but it is uncomfortable, since before this they were giving me error 500, but with a try-catch I solved it, but now from time to time it throws this error.

Do you webpack your lambda resolver(s) before you upload it to the Dgraph server? If yes, check what’s in your package.json. In most cases a good rule of thumb is not to use many external packages, since most (lambda) operations can be done natively with via node anyway.

1 Like

Thanks, but I don’t webpack the lambda resolvers before upload it to the Dgraph server.