We’re experiencing an issue with our Shopify plugin where GraphQL requests failing since morning today. The error we receive is:
Http request error, no response available: GraphQL Client: fetch failed Error: Http request error, no response available: GraphQL Client: fetch failed at Object.throwFailedRequest (/shopify/node_modules/lib/clients/common.ts:109:11) at NewGraphqlClient.request (/shopify/node_modules/lib/clients/admin/graphql/client.ts:133:7) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) type: HttpRequestError
This occurs during normal plugin operations when trying to fetch or update data via the Admin GraphQL API.
Has anyone else encountered this? Are there known causes or recommended workarounds to prevent these fetch failures?
We’re using the latest @shopify/admin-graphql client in a Node.js environment. We’re looking for insights on what typically causes this in Shopify plugins. Could it be related to rate limits, network instability, or something else in GraphQL client usage?
Hey @anshika_koul! I haven’t seen any other recent reports of this internally, looks like it might be a network/infrastructure issue on your end. “No response available” means the request is failing before it even gets to Shopify’s servers.
I’ve seen this exact error reported in the public shopify-app-js repo in the past where it only happened in production and was intermittent - ultimately resolved by changing hosting setup.
It’d also be worth checking firewalls or proxies as they can sometimes block outbound connections
DNS resolution would be another thing to look at - anything strange there? If you manage to figure it out let us know what did the trick!
Hi @Donal-Shopify - thanks for the quick reply. following up on our earlier discussion about the Http request error – no response available: fetch failed issues:
We’ve gathered more diagnostics on our side, and dug a bit more and I’d like to share the findings as they may help pinpoint what’s happening.
We are seeing a large number of timeouts when making Admin GraphQL API calls, particularly for our largest customers since morning.
Our Datadog APM traces show a very distinct pattern like p99 and max latency are consistently ~10 seconds, and this latency spikes correlate 1:1 with the error graphs in our application logs.
Not all requests are affected, but the ones that fail all hover very close to the 10-second timeout threshold. data shows that the distribution of latency jumps dramatically only for these large stores starting around the same time this morning.
We understand from your previous response that “no response available” typically means the request never reached Shopify.
However, looking at Datadog and APM data we see that :
A significant number of requests do reach Shopify and succeed normally.
But another subset stalls exactly until the timeout (≈10s).
These timeouts are new and started suddenly today around 07:57.
Is it expected that large stores (high order volume / high query complexity) might occasionally experience connection-level stalls before a request is processed? or what could cause these?
also we confirmed that we do not have a 10-second timeout configured in our GraphQL client.
This makes us suspect that the ~10s timeout is coming from either a connection drop from Shopify’s edge / load balancer layer.
would appreciate your help to understand what could cause connection-level stalls on the Shopify side.
Thanks for that additional context! The fact that it started at a specific time and affects large stores specifically suggests something worth investigating on our end. To dig into this properly, can you share:
API client ID - you can find this in your Partner Dashboard under your app
Shop IDs (myshopify.com domain or shop ID) for 2-3 affected stores
Exact timestamps (with timezone) when the timeouts occurred for each example store
(If you’d prefer to share these privately, you can open a support ticket mentioning this thread and it’ll get routed to Developer Support)
With those details we can check our logs and loop in our infrastructure teams if need be. Thanks!
Hi @Donal-Shopify Thanks for the follow-up! It looks like the process has shifted slightly on our end
we had to speak with someone on the chat, and explain all this and Shopify will now be reaching out to us directly via email. Once we receive that message, we’ll be able to reply with the API client ID, affected shop domains, and the exact timestamps you requested.
We were planning to share those details here earlier, but we’ll wait for the email so everything stays tied to the correct support thread.
Appreciate you looking into this we’ll respond as soon as the email comes through.
I’m experiencing the same issue as anshika_koul. It occasionally fails for unclear reasons. I’ve tried to reproduce and investigate it in my code, but the issue is difficult to replicate consistently.
Hey @Lisandro_Phan, Anshika reached out to support who were able to check the logs. Feel free to do the same, sharing the below info along with a description of the observed behavior and they’ll be happy to review!
You can do so via our Help Center by clicking Chat with a human. Explain the issue to the Support Advisor, share the details listed above, and they’ll get it to the Developer Support team for further investigation. Thanks Lisandro!
I have a quite similar problem as mentioned by @anshika_koul . it happens whenever i make the api call thru the @shopify/shopify-api REST/GraphQL clients.
Hi Kit_Yuen, I’m not using /shopify-app-express in my codebase. Given the logged error (fetch failed), it seems likely that the issue is on Shopify’s server side rather than in my implementation. But it’s sometime not usually.
