@kapa.ai are you aware of any shopify connector issue ? our fulfillment_orders table has slowed done, normally a synch takes 10 min, but since 2025-12-16 it takes 2 hrs, and not it is up to 40 hrs, any idea why ?

There are a few Shopify‑connector‑related items in the knowledge you shared, but none describe a known bug that specifically makes the

fulfillment_orders

stream suddenly grow from 10 minutes to 40 hours starting around 2025‑12‑16. What we do know: - The Shopify source has known performance limitations due to Shopify API rate limits and how some sub‑streams are implemented (e.g., per‑object calls, 1–2 requests/second in some cases). In earlier versions, this led to “1 record per second” behavior on some streams like

inventory_item

and others, and there wasn’t much that could be done beyond respecting Shopify’s limits.[\[Shopify slow](https://discuss.airbyte.io/t/338)\] - A user with large Shopify stores reported severe memory and performance issues on “child” streams such as

transactions

,

order_refunds

,

fulfillment_orders

, especially on big stores (150k+ orders/customers), where these streams iterate over all parent objects and can consume a lot of resources.[\[Child streams memory](https://discuss.airbyte.io/t/3553)\] - Starting from 2.0.0, the connector introduced GraphQL BULK operations specifically to speed up

Fulfillment Orders

and other streams.[\[Shopify 2.0.0](https://docs.airbyte.com/integrations/sources/shopify-migrations#upgrading-to-200)\] There’s no note in the provided changelog that a later version regressed

fulfillment_orders

performance, but only general “update dependencies” or bug‑fix notes.[\[Shopify changelog](https://docs.airbyte.com/integrations/sources/shopify#changelog)\] - The limitations/troubleshooting section confirms that rate limiting and BULK operation restrictions can cause retries and backoff, which can significantly prolong syncs when Shopify is throttling more often.[\[Shopify limits](https://docs.airbyte.com/integrations/sources/shopify#limitations--troubleshooting)\] Given that: - The knowledge you’ve provided does not mention: - Any incident or bug on or after 2025‑12‑16 that specifically affects

fulfillment_orders

. - A regression tied to a particular Shopify connector version on that date. So I cannot point to a documented, known issue that clearly explains your sudden jump from 10 minutes to 2 hours and now 40+ hours. Based on what is documented, here are the next steps that are most aligned with existing guidance: 1. Check your Shopify connector version and recent upgrades - See if you recently upgraded from a pre‑2.0.0 version to 2.x/3.x, or between recent 3.x versions where dependencies changed.[\[Shopify changelog](https://docs.airbyte.com/integrations/sources/shopify#changelog)\] - If you did a connector upgrade just before 2025‑12‑16, that’s a strong suspect, even if we don’t have a specific regression note in the docs. 2. Confirm whether

fulfillment_orders

is using BULK - BULK for

Fulfillment Orders

was introduced in 2.0.0 and is supposed to increase performance.[\[Shopify 2.0.0](https://docs.airbyte.com/integrations/sources/shopify-migrations#upgrading-to-200)\] - If you’re on ≥2.0.0 and seeing extreme slowness, logs may show: - Many repeated 429 / rate‑limit warnings with exponential backoff, or - BULK jobs failing and falling back to slower behavior. - The documentation says it’s expected to see retry/backoff messages when hitting rate limits.[\[Shopify limits](https://docs.airbyte.com/integrations/sources/shopify#limitations--troubleshooting)\] 3. Inspect logs for rate‑limit / BULK issues Look in the sync logs for: -

429

or “Rate Limit Exceeded”. - Messages like “The BULK job couldn’t be created at this time, since another job is running.”, or instructions to check BULK operation progress.[\[Shopify limits](https://docs.airbyte.com/integrations/sources/shopify#limitations--troubleshooting)\] If you see these repeatedly, the runtime increase is likely caused by: - Shopify throttling more aggressively (e.g., business‑side load, new apps, or other integrations), or - Many BULK jobs being retried/queued. 4. Isolate the

fulfillment_orders

stream Similar to prior recommendations for other slow connectors, you can try: - Creating a connection that syncs only the

Fulfillment Orders

stream, to: - Confirm the slowness is isolated to this stream. - See if it behaves more stably when run alone (fewer concurrent API calls across streams). A similar “one stream per job” recommendation was given for Shopify in other contexts.[\[Shopify slow](https://discuss.airbyte.io/t/338)\] 5. Check resource usage - For large Shopify stores, child streams like

fulfillment_orders

have been known to blow up memory usage and kill jobs on big datasets.[\[Child streams memory](https://discuss.airbyte.io/t/3553)\] - Verify if your sync pods / containers are CPU‑ or memory‑bound during the job. If they are hitting limits, you may need to increase resource requests/limits and re‑run. 6. If nothing obvious shows up: open an issue with logs Since the shared knowledge does not list a known

fulfillment_orders

regression around your date, the safest path is: - Open an issue in the

airbytehq/airbyte

repo with: - Your Airbyte version. - Shopify connector version. - Approximate store size (orders, customers). - Before/after runtimes. - A recent sync log (for a run that took many hours). - This is how similar Shopify connector issues (performance, failures, memory build‑up) have been escalated and debugged in the past.[\[Shopify to MySQL](https://discuss.airbyte.io/t/338);\[Child streams memory](https://discuss.airbyte.io/t/3553)\] Because the current knowledge does not contain a specific, confirmed bug matching “`fulfillment_orders` suddenly going from 10 minutes to 40 hours on 2025‑12‑16”, I can’t definitively say why it changed in your environment. The leading candidates, based on prior reports, are: - Increased throttling or changed rate‑limit behavior on Shopify’s side. - A recent Shopify connector upgrade changing behavior/performance. - Large growth in the underlying data (orders/fulfillments) causing child‑stream fan‑out to explode. - Resource constraints or failures causing repeated retries. If you can share the connector version and whether it was upgraded around that date, I can help you map that to the specific changes listed in the Shopify migration guide and changelog.