@pawan and @rajas, I’m continuing to experience this issue. I’ve also tested it out on a separate interface query that my schema generates (querySpecimen, also available in the link to the schema I posted in the prior message) but I can’t get it to return any data. I’m getting a 200 status back but "data": { "querySpecimen": [] } is the payload.
Basically, what seems to be happening is that querying on the interface types using the generated query is failing. I don’t have @auth defined on those interfaces because last I heard it was not supported yet - maybe that’s changed or is the core of my issue?
EDIT: I’m also just encountering errors in general now with queries that sort of work but the @auth definition I provided does not seem to actually be filtering properly - e.g. for queryOwnerOrg all OwnerOrg types are being returned, not just the ones that receive a request with a JWT containing a custom claim of orgID matching their own ID field. I feel like I’ve missed something on how the auth definitions should be working…