@KittenMania was the step Enrich with an API’s error message “API Enrichment took longer than 3600s”? If so or similar, this is due to Parabola having a 1-hour timeout on any flow step, meaning our call to the API’s endpoint to receive or send data (rows) stops after 1 hour.
Given your row amount, to make your flow run quicker while avoiding errors, I’d advise switching to a different Shopify InventoryItem endpoint in the API enrichment step for product cost information (change from using the endpoint that
retrieves a single inventory item by ID to the one that
retrieves a list of inventory items).
New flow structure does ID batches to prevent timeout or max request errors:
After the Shopify import brings in selling price data, connect it to
Insert row numbers to get a column of repeated numbers (i.e. the number 1 on 100 of the rows, then the number 2 on the next 100 rows, etc). Then
Select columns to only keep row numbers and the variant inventory item IDs.
Merge duplicate rows to get the inventory column of rows with merged ID batches (instead of one row per item ID we get one row per 100 item IDs). Connect this to the Enrich with an API noting the limit of
100 rows in the URL parameters and the top level key of
intentory_items. You’d finish by combining the results from API enrichment back to the main Shopify imported data to have both
variants: price columns.
This Limit rows method will be prone to more errors, but if you’d like to continue trying it, set its settings to
Keep the first 7200 rows or less so it’s within our 1hr timeout limit (7200 rows ÷ 120 requests per min = 60min). This is because Shopify’s API rate limits are
120 requests/min for the max value to use in
Enrich with an API > Rate Limiting > Maximum requests per min. Update these step settings in the initial version’s flow structure: