Identified - Our crawl data vendor is experiencing an issue which is intermittently preventing us from refreshing Walmart Canada crawl data with them. This outage affects all product reports and the price history widget for Walmart CA.
Walmart US is not affected with this incident.
Merchandising, compliance, buy box, and map violation reports may have stale product data, and data gaps in the price history widget may be present until the outage is resolved.
We’ve escalated the issue with our vendor and they are working towards a resolution.
Once the issue has been resolved, all product data will automatically be refreshed within the next 24 hours, but we will not be able to backfill the data gaps in the price history widget.
Resolved -
Our team has corrected the issue causing Custom Integrations, Password Protected Catalogs/Lightboxes, and access to Labs, these should be working as expected now. Failed Custom Integrations processes should re-run as expected in the next scheduled run. If you are still having issues accessing the Labs or Password Protected Catalogs/Lightboxes, please try to clear your browser's caches and cookies before retrying. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
May 12, 09:13 EDT
Update -
Our team has corrected the issue causing Custom Integrations, Password Protected Catalogs/Lightboxes, and these should be working as expected now. Access to Labs may still fail with an authentication error, and our team is actively working on correcting this. We hope to have this done as soon as possible. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
May 12, 06:34 EDT
Update -
We are continuing to investigate this issue.
May 12, 06:00 EDT
Investigating -
Our engineering team has identified and is addressing an issue that is causing Custom Integrations, Password Protected Catalogs/Lightboxes, and access to Labs to fail with an authentication error. We hope to have this done as soon as possible. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
May 12, 05:50 EDT
Resolved -
Our engineering team found an issue with the connection to our FTP partner which resulted in a partial outage from from 05:27AM to 08:25AM UTC. The connection to the FTP has been re-established, and the issue is now resolved. This could cause FTP Imports pulling from the Salsify FTP and Channel publishes to the Salsify FTP to fail. As well as any Custom Integrations that rely on our FTP as a source or destination. Upon failure, Channel deliveries will retry twice, then wait until the next scheduled publish; imports and integrations will also retry and wait until the next scheduled run if fail, or can be re-ran manually. We apologize for the inconvenience. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
May 11, 07:22 EDT
Monitoring -
Our engineering team found an issue with the connection to our FTP partner which resulted in a partial outage from from 05:27AM to 08:25AM UTC. The connection to the FTP has been re-established, but our team is still monitoring. This could cause FTP Imports pulling from the Salsify FTP and Channel publishes to the Salsify FTP to fail. As well as any Custom Integrations that rely on our FTP as a source or destination. Upon failure, Channel deliveries will retry twice, then wait until the next scheduled publish; imports and integrations will also retry and wait until the next scheduled run if failed, or can be re-ran manually. We apologize for the inconvenience. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
May 11, 05:43 EDT