- Detected by Pingoru
- Jun 03, 2026, 02:42 PM UTC
- Resolved
- Jun 03, 2026, 04:00 PM UTC
- Duration
- 1h 17m
Affected: Syndication
Timeline · 3 updates
-
identified Jun 03, 2026, 02:42 PM UTC
Our engineering team identified that Shopify has an active incident. As we receive updates from Shopify of a resolution, we will provide further updates. No other syndication channels are affected at this time. If you have any questions, please use the "My Cases" option within the Customer Portal https://help.salsify.com/ProductXM/s/ to connect with our team.
-
monitoring Jun 03, 2026, 03:26 PM UTC
Our engineering team identified that Shopify has an active incident. As we receive updates from Shopify of a resolution, we will provide further updates. No other syndication channels are affected at this time. If you have any questions, please use the "My Cases" option within the Customer Portal https://help.salsify.com/ProductXM/s/ to connect with our team.
-
resolved Jun 03, 2026, 04:00 PM UTC
Shopify has resolved their active incident, and we are seeing successful syndications in Salsify using the Shopify GQL integration. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 07:58 AM UTC
- Resolved
- Jun 04, 2026, 10:46 AM UTC
- Duration
- 2d 2h
Affected: Amazon
Timeline · 3 updates
-
investigating Jun 02, 2026, 07:58 AM UTC
We are currently investigating an issue where publications to Amazon Vendor Central and Seller Central are failing across multiple marketplaces and product types. Affected users are receiving a submission error stating that the 'Is Refurbished' attribute is required but missing, despite the attribute not being available within the channels. Our engineering team is actively researching the root cause to determine a resolution, and we will provide updates as soon as more information becomes available. If you have any questions, please use the “My Cases” option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
identified Jun 02, 2026, 12:52 PM UTC
Our engineering team has identified the issue causing the 'Is Refurbished' attribute from appearing in the Amazon Vendor Central and Seller Central channels. This attribute is now appearing in the Amazon Vendor Central US channels. The team is working to update the affected channels to unveil this attribute and we will provide updates as soon as more information becomes available. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
resolved Jun 04, 2026, 10:46 AM UTC
Our engineering team has identified the issue causing the 'Is Refurbished' attribute from appearing in the Amazon Vendor Central and Seller Central channels. All available Amazon and Seller Central channels have been refreshed and the attribute is now appearing as expected. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:02 PM UTC
- Resolved
- Jun 09, 2026, 05:57 PM UTC
- Duration
- 7d 22h
Affected: Syndication
Timeline · 4 updates
-
identified Jun 01, 2026, 07:02 PM UTC
We ask that any brands with the HEB Direct Connection channel activated in their Saslify web-app, not execute any publishes via that channel, at this time. Our engineering teams are working on resolving an issue that was recently identified within this connection. In partnership with HEB, we've determined a solution and are working to deliver it, as soon as possible. Please contact Salsify Support if you have any further questions.
-
identified Jun 02, 2026, 08:03 PM UTC
We ask that any brands with the HEB Direct Connection channel activated in their Salsify web-app not execute any publishes via that channel at this time. Our engineering teams continue to work on resolving an issue that was recently identified within this connection. In partnership with HEB we've determined a solution and are working to deliver it as soon as possible. Please contact Salsify Support if you have any further questions.
-
identified Jun 05, 2026, 04:27 PM UTC
We ask that any brands with the HEB Direct Connection channel activated in their Salsify web-app not execute any publishes via that channel at this time. In partnership with HEB we have determined a solution and are working to verify and deliver it as soon as possible. Please contact Salsify Support if you have any further questions.
-
resolved Jun 09, 2026, 05:57 PM UTC
Our engineering team has resolved the issue impacting our HEB Direct Connection channel. Brands can now resume publishing products via the HEB Direct Connection channel. If you encounter any issues or have questions regarding this incident, please contact Salsify Support.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 12:38 PM UTC
- Resolved
- Jun 08, 2026, 03:02 PM UTC
- Duration
- 17d 2h
Affected: Walmart
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 02:23 AM UTC
- Resolved
- Apr 29, 2026, 02:23 AM UTC
- Duration
- —
Affected: Syndication
Timeline · 1 update
-
resolved Apr 29, 2026, 02:23 AM UTC
Our engineering team has resolved an issue that affected the Facebook Catalog Direct and Instagram connections for approximately 12 hours, starting April 28, 2026, at 14:09 GMT+1. During this window, publications to these specific channels may have failed. We have implemented a fix and confirmed that the systems are now stable and operating as expected. If you had a publication fail during this time, please republish your content to ensure it is successfully delivered. No other syndication channels were impacted by this issue. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 05:55 PM UTC
- Resolved
- Apr 22, 2026, 02:33 PM UTC
- Duration
- 20h 37m
Affected: The Home Depot
Timeline · 3 updates
-
investigating Apr 21, 2026, 05:55 PM UTC
We are investigating reports of the following feedback being returned in the Home Depot direct connection: 'Unable to prepare target system for upload. Unexpected answer received: 403' We have escalated this issue to Home Depot. The feedback has been reported starting yesterday April 20th. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
monitoring Apr 22, 2026, 10:17 AM UTC
Our Home Depot partners have implemented a fix for the issue that was causing 403 error responses following channel publishes. We have confirmed that publishing functionality has returned to expected levels. We request that any customers who experienced failed publishes during this time manually republish their channels to confirm resolution. Our engineering team will continue to monitor the connection and system stability closely to ensure performance remains consistent. We will provide a final update once we have full confidence in the resolution. If you have any questions, please use the "My Cases" option within the Customer Portal ([https://help.salsify.com/ProductXM/s/](https://help.salsify.com/ProductXM/s/)) to connect with our team.
-
resolved Apr 22, 2026, 02:33 PM UTC
Our Home Depot partners have deployed a fix and the issue is now confirmed resolved. If you have not yet republished, please do so to confirm. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 10:34 PM UTC
- Resolved
- Apr 17, 2026, 03:53 PM UTC
- Duration
- 17h 19m
Affected: Salsify Application
Timeline · 3 updates
-
investigating Apr 16, 2026, 10:34 PM UTC
We are investigating reports of Product and Asset Lists losing their filters when renaming the List. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
monitoring Apr 17, 2026, 12:18 AM UTC
We have identified the cause of the issue, and have temporarily disabled the new List Experience so as to ensure no further filter removals across organizations. We are monitoring for continued success. If you have any questions, or believe a list was impacted by this incident, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
resolved Apr 17, 2026, 03:53 PM UTC
The incident affecting Smart List Filter Removal has been resolved, and the new List UI has been re-enabled. If you have any questions, or believe your list may have been impacted, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 06:06 PM UTC
- Resolved
- Apr 16, 2026, 07:50 PM UTC
- Duration
- 1h 43m
Affected: Salsify ApplicationCatalog Sites
Timeline · 3 updates
-
investigating Apr 16, 2026, 06:06 PM UTC
We have identified an issue that causes blank zip files when exporting Digital Asset Feeds and Digital Assets from Sites & Classic Catalogs. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
monitoring Apr 16, 2026, 06:42 PM UTC
We have identified and corrected an issue that was generating blank zip files when exporting Digital Asset Feeds and Digital Assets from Sites & Classic Catalogs. If you continue to see issues with generating a Digital Asset export, please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Apr 16, 2026, 07:50 PM UTC
This issue has been resolved. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 09:22 AM UTC
- Resolved
- Apr 17, 2026, 09:22 AM UTC
- Duration
- 1d
Affected: Enhanced ContentWalmart
Timeline · 4 updates
-
investigating Apr 16, 2026, 09:22 AM UTC
We have identified an issue causing all publications via the Walmart 1P (Vendor) connector to fail due to an error retrieving credentials from Walmart's API. This appears to be related to an outage on Walmart's side. Walmart 3P (Marketplace) services appear to be unaffected at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
investigating Apr 16, 2026, 01:55 PM UTC
We are currently investigating an issue causing publications via the Walmart 1P (Vendor) connector to fail due to an error retrieving credentials from Walmart's API. This issue also impacts Enhanced Content publishes for customers utilizing OAuth authentication with Walmart’s API Gateway.Walmart 3P (Marketplace) services using legacy authentication appear to be unaffected at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
monitoring Apr 16, 2026, 11:23 PM UTC
Walmart has reported progress in resolving the internal errors that have been broadly impacting supplier API submissions. As of 6:40 PM WET (1:40 PM EDT), our engineering team has observed the first successful publications through the Walmart 1P (Vendor) and Enhanced Content (OAuth) connectors. While this indicates that the service is recovering, we are continuing to monitor the success rate to ensure stability across all accounts. Action Required for Failed Submissions: Please note that any publications that failed prior to this recovery window will not automatically reprocess. Please republish the affected products to transmit them to Walmart. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for assistance or questions.
-
resolved Apr 17, 2026, 09:22 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 08:27 PM UTC
- Resolved
- Apr 14, 2026, 09:35 PM UTC
- Duration
- 1h 8m
Affected: Salsify Application
Timeline · 3 updates
-
investigating Apr 14, 2026, 08:27 PM UTC
We are investigating issues with one of our model providers, manifesting as delayed Kroger Publications. Additionally, users leveraging Intelligence Suite Workflows may be experiencing an increase of Task Failures. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
monitoring Apr 14, 2026, 08:58 PM UTC
The model issue affecting delayed Kroger Publications and Intelligence Suite Workflow Failures has been corrected. We are monitoring for continued success, and final confirmation from our provider. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Apr 14, 2026, 09:35 PM UTC
This issue has been resolved. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 02:59 PM UTC
- Resolved
- Mar 17, 2026, 04:00 PM UTC
- Duration
- 1h
Affected: Salsify Application
Timeline · 3 updates
-
investigating Mar 17, 2026, 02:59 PM UTC
Product detail pages may be failing to load. Error "unable to load properties" appears. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
monitoring Mar 17, 2026, 03:12 PM UTC
We have addressed an issue which was causing product detail pages to fail with error "unable to load properties." We are continuing to monitor at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Mar 17, 2026, 04:00 PM UTC
We addressed an issue which was causing product detail pages to fail with error "unable to load properties." Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 08:51 PM UTC
- Resolved
- Mar 12, 2026, 10:16 PM UTC
- Duration
- 1h 24m
Affected: GDSN
Timeline · 2 updates
-
identified Mar 12, 2026, 08:51 PM UTC
We have identified an issue when load publishing GDSN data to the Salsify data pool. Previously existing data pool validation errors are not clearing, after the previously identified/reported data discrepancies have been addressed. Our engineering team has identified the problem and is currently in the process of applying a fix.
-
resolved Mar 12, 2026, 10:16 PM UTC
The issue impacting GDSN load publishes (which prevented data pool validations from clearing) has been resolved. If you have GTINs that were impacted by this issue, please load publish those GTINs to our data pool again. If you encounter any further issues of this nature, please reach out to Salsify Support.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 04:15 PM UTC
- Resolved
- Apr 10, 2026, 03:29 PM UTC
- Duration
- 35d 23h
Affected: Syndication
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 04:30 PM UTC
- Resolved
- Mar 04, 2026, 07:31 PM UTC
- Duration
- 3h
Affected: Salsify Application
Timeline · 3 updates
-
investigating Mar 04, 2026, 04:30 PM UTC
Our engineers are investigating long-queuing imports, and delayed bulk edit actions and subscription triggers. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
monitoring Mar 04, 2026, 06:19 PM UTC
Our engineers have identified and addressed an issue which was causing long-queuing imports, as well as delayed bulk edit actions and subscription triggers. Operation times should be returning to normal. We are continuing to monitor closely. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Mar 04, 2026, 07:31 PM UTC
Our engineers identified and addressed an issue which caused long-queuing imports, as well as delayed bulk edit actions and subscription triggers. Operation times have returned to normal. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 10:28 PM UTC
- Resolved
- Mar 06, 2026, 04:58 PM UTC
- Duration
- 3d 18h
Affected: Salsify FTP
Timeline · 2 updates
-
monitoring Mar 02, 2026, 10:28 PM UTC
On March 2, 2026 at approximately 9:00PM UTC, multiple connection failures occurred when processing imports from and exports to the Salsify FTP. The connection errors appear to be resolved as of 9:30PM UTC. We are continuing to monitor the imports and exports connecting to the Salsify FTP to ensure this does not occur again. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Mar 06, 2026, 04:58 PM UTC
Through our monitoring, we have seen stable connections to the Salsify FTP since March 2, 2026 at 9:30PM UTC. Publication to the Salsify FTP and imports of files from the Salsify FTP are completing successfully without any issues. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 09:37 PM UTC
- Resolved
- Feb 25, 2026, 06:05 PM UTC
- Duration
- 5d 20h
Affected: Enhanced ContentWalmart
Timeline · 2 updates
-
identified Feb 19, 2026, 09:37 PM UTC
We identified an issue with syndicating Enhanced Content to Walmart US. We have reached out to our partners at Walmart to further identify the root cause and an estimated time for resolution. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Feb 25, 2026, 06:05 PM UTC
We are now seeing successful syndications of Enhanced Content to Walmart US. If you experienced Enhanced Content not going live on Walmart US during this Incident, we encourage you to republish the layout. If you continue to see Enhanced Content not go live on Walmart US, please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions or further investigation.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 05:43 PM UTC
- Resolved
- Jan 09, 2026, 06:36 PM UTC
- Duration
- 52m
Affected: Salsify Application
Timeline · 2 updates
-
investigating Jan 09, 2026, 05:43 PM UTC
Our engineers are investigating reports of system slowness, delays in import and export queueing, and failed requests. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Jan 09, 2026, 06:36 PM UTC
Our engineers addressed an issue which was causing platform slowness and failed requests, and system performance is back to normal levels. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Read the full incident report →
- Detected by Pingoru
- Dec 09, 2025, 04:10 PM UTC
- Resolved
- Dec 09, 2025, 05:03 PM UTC
- Duration
- 52m
Affected: Imports and Indexing
Timeline · 3 updates
-
investigating Dec 09, 2025, 04:10 PM UTC
We are experiencing slowness in imports, adding products to smart and simple lists, and filtering for products using newly added property values. Our engineering team is investigating the issue causing the delays and queuing. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
monitoring Dec 09, 2025, 04:43 PM UTC
We have observed that import runs are now processing normally. Our engineering team continues to monitor the system to ensure all services—including product list additions and filtering—remain stable and fully operational. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
-
resolved Dec 09, 2025, 05:03 PM UTC
We have confirmed that imports, product list additions, and filtering are all processing normally. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Read the full incident report →
- Detected by Pingoru
- Dec 01, 2025, 11:17 PM UTC
- Resolved
- Dec 02, 2025, 05:35 AM UTC
- Duration
- 6h 17m
Affected: Syndication
Timeline · 3 updates
-
investigating Dec 01, 2025, 11:17 PM UTC
We have detected an issue impacting publications from our Kroger New Item Setup and Partial Content Refresh channels. It appears to related to a third party provider. Our engineers are investigating the issue and exploring the impact with them. We will update as soon as we know more.
-
investigating Dec 02, 2025, 12:50 AM UTC
We are continuing to investigate this issue.
-
resolved Dec 02, 2025, 05:35 AM UTC
The root cause of the failed Kroger publishes has been resolved. Any publish that failed recently, with no feedback returned, will need to be attempted again. Please contact Support if you continue to encounter issues of this nature.
Read the full incident report →
- Detected by Pingoru
- Nov 19, 2025, 02:03 AM UTC
- Resolved
- Nov 19, 2025, 03:27 AM UTC
- Duration
- 1h 24m
Affected: Readiness Reports
Timeline · 2 updates
-
monitoring Nov 19, 2025, 02:03 AM UTC
Our engineering team has identified an issue where an Error was returned when editing mappings in Readiness Reports. A subsequent update has resolved this and we continue to monitor the system to ensure stability. If you have any questions, please use the “My Cases” option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
resolved Nov 19, 2025, 03:27 AM UTC
We have been monitoring the Readiness Reports behaviour closely, and have confirmed with multiple users that mapping working as expected. If you have any questions, please use the “My Cases” option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 05:30 PM UTC
- Resolved
- Nov 18, 2025, 06:41 PM UTC
- Duration
- 1h 11m
Affected: Salsify Application
Timeline · 2 updates
-
monitoring Nov 18, 2025, 05:30 PM UTC
We received reports that some users were unable to save Formulas on Channel Attributes, and a fix has since been pushed to correct this experience. We are monitoring for continued success. Users are able to save Formulas on Channel Attributes at this time. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions regarding this topic.
-
resolved Nov 18, 2025, 06:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:58 AM UTC
- Resolved
- Oct 21, 2025, 09:02 AM UTC
- Duration
- 23h 3m
Affected: Salsify Application
Timeline · 6 updates
-
monitoring Oct 20, 2025, 09:58 AM UTC
Following an earlier outage originating from our infrastructure provider, access to the Salsify platform has been restored. Users should now be able to log in and access the application. We are continuing to monitor the situation closely to ensure stability. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ if you continue to experience issues or have questions.
-
monitoring Oct 20, 2025, 09:59 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Oct 20, 2025, 02:17 PM UTC
Our infrastructure provider is still experiencing issues as they work to fully recover all services. We are still seeing some impacts from this, to the Salsify platform. We continue to monitor closely and will provide further updates as we have them Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions
-
monitoring Oct 20, 2025, 07:08 PM UTC
Our infrastructure provider is making progress toward full recovery of all services. We are continuing to monitor closely and will provide further updates as we have them. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions regarding this topic.
-
monitoring Oct 20, 2025, 10:22 PM UTC
Our infrastructure provider is making progress towards full resolution, and we continue to monitor. Our next update will be provided tomorrow morning around 4AM EST. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions regarding this topic.
-
resolved Oct 21, 2025, 09:02 AM UTC
Our infrastructure provider has confirmed a full recovery of their services and this incident is now resolved. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions regarding this topic.
Read the full incident report →
- Detected by Pingoru
- Oct 15, 2025, 07:15 PM UTC
- Resolved
- Oct 16, 2025, 09:21 PM UTC
- Duration
- 1d 2h
Affected: Salsify ApplicationReadiness ReportsCatalog Sites
Timeline · 4 updates
-
investigating Oct 15, 2025, 07:15 PM UTC
Our engineers are investigating issues with slowness when exporting from Salsify. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions regarding this topic.
-
investigating Oct 15, 2025, 07:31 PM UTC
Our engineers are investigating issues with slowness when exporting or publishing from Salsify. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions regarding this topic.
-
monitoring Oct 15, 2025, 08:57 PM UTC
Export and publication performance has returned to normal. Our engineers are continuing to monitor at this time. Please reach out to customer support at https://help.salsify.com/ProductXM/s/ for any questions regarding this topic.
-
resolved Oct 16, 2025, 09:21 PM UTC
This incident has been resolved.
Read the full incident report →
Critical September 29, 2025 - Detected by Pingoru
- Sep 29, 2025, 08:59 AM UTC
- Resolved
- Sep 29, 2025, 08:59 AM UTC
- Duration
- —
Affected: Walmart
Timeline · 3 updates
-
investigating Sep 25, 2025, 09:49 PM UTC
We are currently experiencing an issue causing Walmart Marketplace publishes to fail. Our engineering team is working in conjunction with Walmart to resolve the issue. Please reach out to customer support at https://support.salsify.com/ for any questions regarding this subject.
-
monitoring Sep 26, 2025, 02:05 PM UTC
Our engineering team has deployed a hotfix to address the issue causing publications to Walmart Marketplace V5 (Walmart Marketplace (Item Spec 5 Direct Connection) - Item Setup and Walmart Marketplace (Item Spec 5 Direct Connection) - Partial Content Refresh schemas) to fail. This change works around the upstream API issue related to access token validation. We have observed initial successful publications following this fix and are now actively monitoring the connection to ensure sustained stability. We are still engaged with our partners at Walmart to understand the root cause of the initial change. Any publications that failed during this incident will need to be republished.
-
resolved Sep 29, 2025, 08:59 AM UTC
Our engineering team has confirmed that the hotfix deployed on Friday successfully addressed the issue causing publications to Walmart Marketplace V5 (Walmart Marketplace (Item Spec 5 Direct Connection) - Item Setup and Walmart Marketplace (Item Spec 5 Direct Connection) - Partial Content Refresh schemas) to fail. Publications have remained stable since the fix, and this incident is now considered resolved. Any publications that failed during this incident will need to be republished. Please contact customer support at https://support.salsify.com/ for any questions related to this subject.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2025, 10:11 AM UTC
- Resolved
- Sep 12, 2025, 03:39 PM UTC
- Duration
- 1d 5h
Affected: Walmart
Timeline · 3 updates
-
investigating Sep 11, 2025, 10:11 AM UTC
We are experiencing a service incident impacting the Walmart Omni Spec Partial Content Refresh connector. This issue is preventing successful content publications. While publications may appear successful within Salsify, they are not being processed by Walmart, which prevents your content from updating. We’ve identified that a recent regular schema update led to the issue, which occurred on September 10, 2025, at 11:00 AM EST. Our team is actively working to revert the connector to the previous version. This is our top priority, and we will provide an update once this mitigation step is complete and the service is restored. We will then conduct a full root cause analysis to apply a permanent resolution before updating the schema again. If you have any questions, please use the “My Cases” option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
monitoring Sep 11, 2025, 04:43 PM UTC
The Walmart Omnispec Partial Content Refresh Connector has been rolled back to the previous version. Publishes are now going through as expected. For any previous publishes that were published yesterday but there is no feedback returned and the updates are not appearing within your Walmart portal, please try republishing again and confirm the publish is completing successfully and there is either feedback being returned or the updates are going through successfully. We will be conducting a full root cause analysis to apply a permanent resolution before updating the schema again. If you have any questions, please use the “My Cases” option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
-
resolved Sep 12, 2025, 03:39 PM UTC
The Walmart Omnispec Partial Content Refresh Connector has been rolled back to the previous version. Publishes are now going through as expected. For any previous publishes that were published on 9/10 but there is no feedback returned and the updates are not appearing within your Walmart portal, please try republishing again and confirm the publish is completing successfully and there is either feedback being returned or the updates are going through successfully. We will be conducting a full root cause analysis to apply a permanent resolution before updating the schema again. If you have any questions, please use the “My Cases” option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.
Read the full incident report →