Shopify Connector / API Limits BC Shopify Connector (Shpfy Communication Mgt., Shpfy GraphQL Rate Limit) → Shopify Admin GraphQL API Shopify docs: GraphQL Admin API rate limits, GraphQL error codes, REST Admin rate limits; BCApps source: Shpfy Communication Mgt. (THROTTLED retry, HTTP 429 retry, telemetry 0000QWH); BCApps PRs #9146 and #10417

Shopify Sync Slow or Failing: API Throttled (THROTTLED / 429 Too Many Requests)

Raw System Error String
THROTTLED: The client has exceeded the rate limit. Similar to 429 Too Many Requests.

What It Means

Shopify limits how much each app can ask per store. The connector uses the GraphQL Admin API, which charges each query a cost in points against a bucket that refills at a set rate by plan (Standard 100, Advanced 200, Plus 1000 points per second). When the bucket is empty, Shopify answers with a THROTTLED error (REST answers HTTP 429 with a Retry-After header). The connector retries automatically, so usually you do not see an error: syncs just get slow. You see an error only if the retries give up, as 'Error(s) on Shopify:' followed by Shopify's error text, on the Shopify Log Entries page.

Root Cause

In codeunit 'Shpfy Communication Mgt.', a GraphQL response that contains THROTTLED is logged (telemetry 0000QWH, 'Shopify GraphQL request %1 was throttled.') and resent after the rate limiter waits. HTTP 429 is retried up to 3 times with a 2-second wait; any other error is raised as 'Error(s) on Shopify:'. Two connector bugs made throttling worse: the rate limiter waited too little after idle time (fixed in PR #9146, seen on a high-volume shop with tens of thousands of throttle events per day) and raw-text GraphQL calls had no pacing (fixed in PR #10417, near-total throttling on small-bucket stores). Many parallel sync jobs, and other apps sharing the store's API capacity, also drain the bucket.

Step-by-Step Fix

  1. Search for 'Shopify Log Entries' (turn on logging on the Shopify Shop Card if needed). Look for entries with Has Error and a Retry Count above 0, and for THROTTLED or 429 in the response.
  2. If you have Application Insights, count telemetry tag 0000QWH ('Shopify GraphQL request ... was throttled') per day to see how often it happens.
  3. Update Business Central to a version that includes the connector fixes from BCApps PRs #9146 and #10417 (better pacing). Check your environment's update in the admin center.
  4. Spread out Shopify sync job queue entries (orders, inventory, products, prices) so they do not all start at the same minute, and do not run more of them in parallel than you need.
  5. Check which other apps on the Shopify store use heavy API traffic at the same times, and move large imports or exports to quiet hours.
  6. For large one-off loads (for example thousands of price changes), let the connector use bulk operations; Microsoft documents that 100 or more price updates run asynchronously on the 'Shopify Bulk Operations' page.
  7. Re-run the failed sync after the bucket refills. Shopify's recommended backoff is one second.

Verification Steps

How to verify: Shopify Log Entries show no new errors with THROTTLED or 429, the 0000QWH count drops, and sync jobs finish within their normal time.

Sources & References

Early Access · 30-Day Sandbox Pilot

Stop Order Sync Failures Before Customers Notice

The Order Flow Doctor monitors Microsoft Dynamics 365 Business Central order flows across Shopify, EDI (TrueCommerce, SPS), 3PLs, and carriers. Get automated root-cause diagnosis and one-click fixes.

We respect your privacy. No spam. You will only be contacted when pilot slots open for your stack.