Shopify – NetSuite order imports failing with "Transaction body is not in correct format" since November 2

Integration Apps
1

From Monday November 2 until the early hours of November 4 (Pacific) I saw this error across many Celigo accounts, not just one — on the Shopify – NetSuite Integration App's order import, before the NetSuite mappings run. It was not caused by anything in your flow, mapping, connection or Shopify order data.

Status: Resolved on November 4, 2026 — Celigo engineering deployed a fix to integrator.io's connection proxy at 2:28 AM Pacific (EU) and 2:32 AM Pacific (NA); no new occurrences since 2:37 AM Pacific.

What the error looked like

Failed to add Shopify Order #1234567890. Transaction body is not in correct format

Failed to add Shopify Order #1234567890. Error Message: Unable to verify response, Status Code: 404

Unable to verify response, Status Code: 404

Cannot read properties of undefined (reading 'transactions')

What I know

  • On the accounts I examined, the flow configuration had not changed and the Shopify orders and their payment transactions were valid when I read them live.
  • Celigo engineering reports the failures only affected shops whose Shopify connection had been migrated to Shopify's expiring access tokens (a change Shopify requires of all apps by January 2027). Those tokens expire every 60 minutes; when one expired in the middle of an order's processing, a defect in the connection proxy's token-refresh path returned the wrong response to the Integration App, which correctly rejected it. The rest of the flow was not blocked.
  • Retries attempted before the fix mostly failed again; most of the affected orders went through on a later run anyway.

What to do now

  1. Nothing to change on your side — re-authorizing the connection or editing mappings was never needed.
  2. If you still have open errors with these messages, retry them now; they will go through. If an order already exists in NetSuite (the error could hit a later re-processing of an imported order), resolve the error instead of retrying.

Reply here if you still see this error on orders from after November 4 — the Celigo team triaging this with me reads every reply.