From 4364d63c4bb0477d518faf529a9a68cd6a4a224c Mon Sep 17 00:00:00 2001 From: "Pablo F. Mescher" Date: Wed, 7 Aug 2024 01:30:14 -0300 Subject: [PATCH] Update quick-start.mdx Added link to graphiql playground --- website/pages/en/quick-start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/pages/en/quick-start.mdx b/website/pages/en/quick-start.mdx index cba2247457b8..d228ce2839d5 100644 --- a/website/pages/en/quick-start.mdx +++ b/website/pages/en/quick-start.mdx @@ -98,7 +98,7 @@ The logs will tell you if there are any errors with your subgraph. The logs of a ![Subgraph logs](/img/subgraph-logs-image.png) -If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly: +If your subgraph is failing, you can query the subgraph health by using the [GraphiQL Playground](https://cloud.hasura.io/public/graphiql?endpoint=https%3A%2F%2Fapi.thegraph.com%2Findex-node%2Fgraphql). Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly: ```graphql {