Sounds like an issue with your team rather than graphql