Context.request is empty in a GraphQL custom resolver

I’ve noticed that context.request is empty in a function which is used as a GraphQL custom resolver,
documentation says that context.request is:

A property that contains information about the external HTTP request that triggered the function call.

So for me it sounds like it should be available in case of custom resolver as well, since it is essentially function call triggered by a request.

Is empty request info in custom resolver a bug or this is an intended behavior?

I also experience same issue but Mongodb team has fixed this issue a few weeks back.

@mo_dew I’ve contacted support some time after I posted this, probably that helped to prioritize the issue, but it was fixed after that. Now the issue looks fixed, at least works fine for my app. Do you still experience the issue?