hasura / hasura/graphql-engine

Hasura Free Cloud Instance is throwing error as soon as "Launch Console" is hit

Open
#10,122 0 comments 0 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version:
CLI Version (for CLI related issue):3

### Environment

Cloud

### What is the current behaviour?
I am using Hasura cloud instance and It has been working fine for last couple of days, Since Today I noticed a weird behaviour when launched the console and tested the graphql queries without any authorization parameter in the query, it worked fine, and but as soon as I added x-Hasura-role and x-hasura-user-id it started to give error as shown in UI.
Subsequent tries without any of the headers (with only the admin key) still resulted in errors.
When I closed the console and reopened the a new console, still i Saw the same issue/error message

![image](https://github.com/hasura/graphql-engine/assets/96169827/8548d41d-9037-4992-bedd-b721e3c4fc9d)

![image](https://github.com/hasura/graphql-engine/assets/96169827/0c019fa1-981a-4e16-b436-5aa75a25e632)

### What is the expected behaviour?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Hasura Cloud issue through Launch Console with the reported x-Hasura-role and x-hasura-user-id headers, then retry with only the admin key and inspect the UI error shown in the screenshots. Done means identifying the cause and restoring console queries for both header configurations.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql
Domain
api, authorization, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.