Connector Improvement: Impact Partner connection enhancements
Answered
Our Impact Partner connection has been experiencing on-going historical sync issues that have incurred high MAR counts. The `catalog_item` endpoint has consistently yielded errors like the following:
We couldn't sync 1 out of the 4 primary endpoint(s). We were unable to sync data for the following tables: [catalog_item_color, catalog_location, catalog, catalog_item_promotion, catalog_item, catalog_item_advertiser_format_categorogies, catalog_service_area]. Error details: {[URL: /{username}/Catalogs; Main Entity: catalog]: Server is not responding with correct response after specific retries and giving status code [500] and status message [<html><title>Server Error</title><body><h1>Server Error</h1><p>The server is temporarily unavailable due to aninternal error. Please notify the system administrator of this problem.
The catalog_item endpoint is a very valuable to join product metadata to our sales data, but this issue seems trigger a historical sync of the entire catalog of items sold, leading to millions of rows syncing. Various tickets have been created to address pagination, cursor improvements, etc. but the error is on-going.
Impact Partner supports affiliate e-commerce data for Walmart, Target, Temu, and others—building out the scalability and capabilities of this connector can make it a great asset to hundreds of companies.
-
Official comment
Hi Joseph,
Thank you for raising a feature request. The request for improving the Impact Partner connector, specifically addressing historical sync performance and reliability on the
catalog_itemendpoint, has been added to our feature improvements backlog.The team is currently investigating the recurring sync failures, and I will share an update as soon as more information is available.
Thanks,
Sanjeevv
Please sign in to leave a comment.
Comments
1 comment