Prisma

does apollo behind the scenes try to fetch the created user record right away to refresh its cache or something?  Or does it have something to do with how I set some private fields in the graphcool permissions?

<@U327M1E6P> The easiest way to debug this is to look at the network traffic in the chrome dev tools. It’s very likely that you are querying some fields on the createUser mutation payload that your do not have the proper permission for

ah that makes sense - now that you mention it I think there is a private field in there

however - does a creatUser mutation always evaluate to an anonymous request?  I do set the auth header in that request with the auth0 id token - but I guess ince the user has not been created yet it’s considered anonymous?

so if you include the token of a user that's already authenticated and then call `createUser`, the request is authenticated. if you call `createUser` with a token from Auth0, that doesn't yet belong to a user, it's not authenticated

also see this feature request, which would be a great addition: <https://github.com/graphcool/feature-requests/issues/139>