Description
The integration attempted to create/update a product, but no corresponding remote product was found. This normally only occurs if creation of the Product Variant Group (PVG) failed or never completed.
Cause
The PVG was not created due to validation errors (missing required fields, invalid characters, duplicate, etc.).
Race condition/latency*: the PVG was created but was not yet searchable when the follow-up product call ran.
Mapping error/omission: the local variant group lacks a linked remoteId to the PVG.
Permission/endpoint error during the PVG call (403/404) or timeout.
A previously created resource was rolled back by the receiving system.
Resolution
If the PVG is missing: create the PVG first, wait briefly (if the system has delayed indexing), then run the product sync again.
Contact Sharespine Support.
* race condition = an error that occurs when the result depends on the order/timing in which two (or more) concurrent operations happen to run. If the order varies, you may get different—sometimes incorrect—outcomes.
latency = delay between cause and effect: network time, queues, database processing, indexing, etc. High latency can mean a newly created resource is not immediately “visible.”
Comments
0 comments
Please sign in to leave a comment.