{"section":"known-issues","requestedLocale":"en","requestedSlug":"infinite-login-loop-when-opening-private-graphiql-link-from-terminal","locale":"en","slug":"infinite-login-loop-when-opening-private-graphiql-link-from-terminal","path":"docs/en/known-issues/Apps/infinite-login-loop-when-opening-private-graphiql-link-from-terminal.md","branch":"main","content":"## Summary\n\nDevelopers are unable to open the private GraphiQL IDE generated by vtex link in VTEX IO development workspaces. Instead of loading the IDE, the browser enters an infinite login loop with VTEX ID and never completes authentication. This affects private GraphiQL routes for linked apps across multiple accounts/workspaces used by developers for testing queries.\n\n## Simulation\n\n1) Link a GraphQL app to a dev workspace (e.g., vendor-invite-graphql or instore-chk-graphql).\n2) Open the private GraphiQL URL from the terminal output.\n3) Observe that the page redirects to the login endpoint (/_v/auth-server/v1/login?ReturnUrl=...) and, after logging in (e.g., with Google), it returns to a page that requests login again, resulting in an infinite loop.\n\n## Workaround\n\nUse the Admin GraphQL IDE for the linked app instead of the private GraphiQL route.\nNavigate to the Admin GraphQL IDE URL and select your linked app from the dropdown."}