I'm a developer helping our fulfilment team migrate from REST to GraphQL so I'm new to using Celigo as an ETL. I've successfully migrated the Shopify export using the GraphQL syntax and I export type set to All products on an hourly basis and import to Netsuite with Add/Update using the ["custrecordproduct_id","is","{{{node.legacyResourceId}}}"]
We keep getting this error on our testing that passes retries but is still worrisome.
"Failed to save record because Unable to save record. Record was change by a different user. Please reload and try again."
Hi Kyle,
As you may know, this is a NetSuite error for when two processes or users are attempting to concurrently make changes to the same record.
Is it possible your existing (non-graphql) flow is also running and attempting to perform updates? Or another flow?
I'd look into the NetSuite connection's concurrency settings in Celigo. Then secondly, look at your NetSuite's concurrency limit (Setup > Integration > Integration Governance).
Hi Kyle, another question for you, from a different angle than Pierce (who has good insight here, def look at those).
Is this a regular biz practice for your client, that multiple people work on records? Or is this more of a one off scenario?
If this is regular, and expected, you can set up a flow to autoretry those specific records that have that situation where edits where made and the NS error appears. Those errors are still logged, but it would eliminate the "noise" of the little ticker counting the errors.
If you want to share the customer name with me via the chat function, i would be happy to assist!
After meeting with Celigo, the pagination settings that the migration wizard automatically sets up for graphQL were incorrect and needed to be configured for a Next Token. Working settings screenshot.
I assume your prior setup was pulling multiple of the same item and thus causing this locking? You attempted to resolve this by setting the concurrency lock, but that lock only applies to a page of data and does not span pages of data. So if you had the same product on other pages, then it would cause this. The default page size is 20, and the default response from Shopify is 50, so I assume this is what was happening.
Additionally, this error gets classified as "intermittent," so they would be auto-retried as long as you have auto-resolve enabled for the flow. That being said, fixing your export was the better solution than relying on auto-retry due to duplicate items coming from the export.
