What was going on
Upgrading hasura/graphql-engine from v2.49.4 to v2.49.5 put the server into a reboot loop with a metadata inconsistency error: Found conflicting definitions for GraphQL type 'UserDeviceGroupUserRole' ... Former has definition: enum UserDeviceGroupUserRole {...} Latter has definition: scalar UserDeviceGroupUserRole. The reporter had the naming_convention experimental feature enabled with HASURA_GRAPHQL_DEFAULT_NAMING_CONVENTION: graphql-default; exporting metadata on v2.49.4 showed no obvious issues.
What fixed it
This was a v2.49.5 regression in the graphql-default naming convention handling , upgrade to v2.50.0, where the reporter confirmed the behavior is gone (maintainer hgiasac suggested exactly that and the reporter closed the issue as resolved). If you must stay on v2.49.x, downgrading back to v2.49.4 was the reporter's temporary workaround. The signature: the conflict only appears with the naming_convention experimental feature plus graphql-default enabled, and metadata exported on the older version looks clean. Source: https://github.com/hasura/graphql-engine/issues/10867