Salsify Outage History

Salsify degraded · 2 long-running issues View live status →

Pingoru has recorded 51 incidents for Salsify: 36 in the last 12 months and 7 in the last 90 days.

Source: status.salsify.com

51incidents recorded
36last 12 months
7last 90 days
4 daystypical duration
Incidents per month
048AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Salsify in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026652 of 720 (7%)
May 20261227 of 744 (31%)
June 20267338 of 720 (47%)
July 20263291 of 744 (39%)
August 20263480 of 744 (65%)
September 20265234 of 720 (32%)
October 20260131 of 744 (18%)
November 202600 of 140 (0%)

Incidents, newest first

Major September 24, 2026 JSON Custom Channel Export failures 1h 48m Salsify Application

Started Sep 24, 2026, 09:14 PM UTC· resolved Sep 24, 2026, 11:02 PM UTC

  1. identified Sep 24, 2026, 09:14 PM UTC

    We are currently investigating an issue causing failures specifically with JSON Custom Channel exports. All other export types and standard features remain fully operational and unaffected. Our engineering team is actively working to resolve the issue. We apologize for the inconvenience and will provide further updates as soon as more information is available.

  2. monitoring Sep 24, 2026, 09:43 PM UTC

    The issue causing failures for JSON Custom Channel exports has been identified and resolved. All export services are now operating normally, and we are monitoring system performance to ensure stability. If you have not yet republished, please do so to confirm.

  3. resolved Sep 24, 2026, 11:02 PM UTC

    The issue causing failures for JSON Custom Channel exports has been identified and resolved. All export services are now operating normally. Any failed Export attempts will require a re-run. 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 →

Minor September 22, 2026 Walmart Rich Media videos not appearing 14d 2h Walmart

Started Sep 22, 2026, 11:07 AM UTC· resolved Oct 06, 2026, 01:39 PM UTC

  1. investigating Sep 22, 2026, 11:07 AM UTC

    We are currently tracking reports about Walmart Rich Media videos not appearing in Walmart's portal or appearing on Walmart's site after a complete, successful publish with no feedback. We have escalated this issue to our Walmart contacts and the issue is currently being reviewed by Walmart's engineering team. We would recommend opening up a Walmart Support case as well to raise awareness while we await for Walmart's assistance on this topic. Please reach out to customer support via email at [email protected] for any questions regarding this subject.

  2. monitoring Oct 02, 2026, 05:29 PM UTC

    Walmart has let us know that they have deployed a fix and resolved the issue on 10/1/26. Please try republishing any affected products and confirm that the videos are appearing live on Walmart's site. Please reach out to customer support via email at [email protected] for any questions regarding this subject.

  3. resolved Oct 06, 2026, 01:39 PM UTC

    Walmart has deployed a fix and resolved the issue on 10/1/26. Please try republishing any affected products and confirm that the videos are appearing live on Walmart's site. Please reach out to customer support via email at [email protected] for any questions regarding this subject.

Read the full incident report →

Notice September 21, 2026 Delay in Kroger publications 5h 39m

Started Sep 21, 2026, 05:17 PM UTC· resolved Sep 21, 2026, 10:56 PM UTC

  1. investigating Sep 21, 2026, 05:17 PM UTC

    We're aware of a delay in all Kroger publications. We are working to understand the root cause and we don't currently have an estimated timeline for resolution. 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.

  2. investigating Sep 21, 2026, 05:20 PM UTC

    We are continuing to investigate this issue.

  3. resolved Sep 21, 2026, 10:56 PM UTC

    The issue impacting Kroger publications has been resolved. Publications impacted by this issue will be completed, and feedback (if any) will be returned to your channel. There is no need to republish unless identifiable feedback was returned to your channel.

Read the full incident report →

Minor September 16, 2026 Intermittent access issues with Salesforce ticketing 23h 26m Salsify Support Portal

Started Sep 16, 2026, 09:58 AM UTC· resolved Sep 17, 2026, 09:25 AM UTC

  1. monitoring Sep 16, 2026, 09:58 AM UTC

    We are currently tracking intermittent access issues with Salesforce, our customer support platform. Users may encounter temporary maintenance messages ("We are down for maintenance") or experience errors when submitting and viewing support cases. Salesforce is actively investigating the issue, and we are monitoring their progress closely to provide updates as soon as they become available. Please reach out to customer support via email at [email protected] for any questions regarding this subject.

  2. resolved Sep 17, 2026, 09:25 AM UTC

    The intermittent access issues affecting Salesforce have been fully resolved. Case management and submission through our Support Portal have returned to normal operation. You can now submit and view cases directly at https://help.salsify.com/help/contact-feedback. Please reach out to customer support at [email protected] if you continue to experience any issues.

Read the full incident report →

Minor August 24, 2026 Delays in data updates and trigger processing 2h 51m Imports and Indexing

Started Aug 24, 2026, 01:22 PM UTC· resolved Aug 24, 2026, 04:14 PM UTC

  1. monitoring Aug 24, 2026, 01:22 PM UTC

    We are currently tracking an issue causing delays in imports. While search performance itself is not impacted, users may experience delays in observing updates through search, as well as delays in updating and processing subscription triggers, workflows, and formulas. Processing queues are actively clearing, and performance will return to normal as the backlog resolves. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. resolved Aug 24, 2026, 04:14 PM UTC

    We have resolved the issue causing delays with system updates, workflows, and trigger processing. System processing throughput has returned to normal levels, and all backlog queues have fully cleared. 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 →

Minor August 18, 2026 Beyond (Bed Bath & Beyond + Overstock) Channel Requirements Update & Publishing Validation Errors 27d 6h Syndication

Started Aug 18, 2026, 05:18 AM UTC· resolved Sep 14, 2026, 12:01 PM UTC

  1. identified Aug 18, 2026, 05:18 AM UTC

    Salsify has identified an issue affecting the Beyond channel connection following recent requirement updates by the retailer. Due to temporary delays in obtaining updated schema templates directly from Beyond, publish requests may result in increased blocking feedback or failed submissions for specific product taxonomies. Salsify teams are actively working to re-establish partner communication channels to acquire the latest specifications. In the interim, impacted users can leverage a Custom Readiness Report to map their Salsify data to Beyond’s requirements and export product content from Salsify to publish directly within the Beyond vendor portal or manage impacted products directly in Beyond’s portal. We will provide our next update as soon as communication with Beyond progresses. 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.

  2. resolved Sep 14, 2026, 12:01 PM UTC

    This issue has been resolved. Salsify has successfully obtained the updated schema templates from Beyond and updated the channel connection with the latest retailer specifications. Product publish requests for Beyond are now processing normally, and users should no longer experience validation errors or submission failures related to and outdated schema. We appreciate your patience while we worked to update the connection. 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 →

Major August 6, 2026 Walmart API Errors & Publication Failures 1d 5h Walmart

Started Aug 06, 2026, 09:40 AM UTC· resolved Aug 07, 2026, 03:36 PM UTC

  1. investigating Aug 06, 2026, 09:40 AM UTC

    We are currently investigating an issue where product publications to Walmart are failing. This stems from an ongoing issue with Walmart's API, specifically impacting their Feeds > Feed item status endpoint. We are actively monitoring Walmart's API status page (https://developer.walmart.com/api-status) and will provide updates as we receive more information. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. investigating Aug 06, 2026, 11:16 AM UTC

    We are providing an update regarding the ongoing Walmart API issue. Impact & Scope Clarification: - Walmart 1P Only: This issue is strictly impacting Walmart 1P connections. Walmart 3P (Marketplace) is unaffected, and publications are flowing through successfully. - Publication Behavior: Product feed submissions are successfully reaching Walmart. However, our integration is failing when retrieving status feedback from Walmart after the feed has been submitted. - What this means for your team: Your product updates are likely going through on Walmart's end, even if Salsify marks the publication as failed. However, if your product feed contains any data errors, that feedback will temporarily not be surfaced within Salsify. Our team is actively investigating the endpoint response errors with Walmart and monitoring for updates. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. monitoring Aug 07, 2026, 10:49 AM UTC

    Walmart's API status page (https://developer.walmart.com/api-status) has now marked their Feeds API as 'Operational'. Publishes for Walmart are now appearing successful. Please try republishing to confirm that the data is flowing as expected. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  4. resolved Aug 07, 2026, 03:36 PM UTC

    Walmart's API status page (https://developer.walmart.com/api-status) has now marked their Feeds API as 'Operational'. Publishes for Walmart are now appearing successful. 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 →

Major July 22, 2026 Amazon Selling Partner Direct Partial Content Refresh for Vendor Central Connection - Cost Price Error 15d 16h Amazon

Started Jul 22, 2026, 11:46 PM UTC· resolved Aug 07, 2026, 03:51 PM UTC

  1. investigating Jul 22, 2026, 11:46 PM UTC

    We are investigating an issue affecting Amazon Selling Partner Direct Connections where Product Change Request (PCR) publications are failing with a 90220 submission error stating that 'Cost Price' is required, even when the value is present in Amazon Vendor Central. While some submissions may process successfully, affected channels display a 'Failed: Publication failed' status. We have escalated this issue directly to Amazon and we are awaiting their feedback. As a temporary workaround, customers can submit affected products using the NIS/FCR connection or manually update product details directly within Amazon Vendor Central. We will provide our next update as soon as new 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.

  2. identified Jul 24, 2026, 12:46 AM UTC

    Amazon has confirmed that they have identified the underlying issue affecting Amazon Selling Partner Direct Connections and are actively working on a resolution. Partial Content Refresh (PCR) publications for the US marketplace are now processing successfully without error. Customers submitting updates for US marketplace channels are encouraged to republish their products to confirm successful transmission. Publications for other reported marketplaces, including Canada (CA) and Great Britain (GB), continue to experience errors. Our team remains in close communication with Amazon as they work toward resolving the issue across all affected regions, and we will provide further updates as new 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.

  3. monitoring Jul 24, 2026, 03:10 PM UTC

    Amazon has deployed a fix which should now resolve the Cost Price error feedback. Please republish any affected products 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.

  4. resolved Aug 07, 2026, 03:51 PM UTC

    Amazon has confirmed that the Cost Price error feedback is now resolved for all reported marketplaces. 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 →

Minor July 16, 2026 Angie & Intelligence Suite errors 2h 50m Salsify Application

Started Jul 16, 2026, 04:04 PM UTC· resolved Jul 16, 2026, 06:54 PM UTC

  1. monitoring Jul 16, 2026, 04:04 PM UTC

    We are encountering intermittent errors when running Intelligence Suite tasks and conversing with Angie. The errors are due to an outage with our AI partner provider. We are monitoring the issue with our AI provider. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. resolved Jul 16, 2026, 06:54 PM UTC

    Our AI partner provider has resolved their outage. We are no longer encountering errors when running Intelligence Suite tasks and conversing with Angie in relation to this outage.

Read the full incident report →

Major July 14, 2026 Home Depot - Customers receiving 503 error response after channel publish 3d 2h The Home Depot

Started Jul 14, 2026, 07:09 PM UTC· resolved Jul 17, 2026, 10:07 PM UTC

  1. investigating Jul 14, 2026, 07:09 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: 503' We have escalated this issue to Home Depot. The feedback has been reported starting today, July 14th 2026. 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.

  2. monitoring Jul 16, 2026, 06:35 PM UTC

    Our Home Depot partners have implemented a fix for the issue that was causing 503 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/) to connect with our team.

  3. resolved Jul 17, 2026, 10:07 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 →

Major June 25, 2026 Accessing API Token via SSO returns 403 error 3d 23h Salsify Application

Started Jun 25, 2026, 07:32 PM UTC· resolved Jun 29, 2026, 07:00 PM UTC

  1. investigating Jun 25, 2026, 07:32 PM UTC

    We have received reports some SSO Users are receiving a 403 response when attempting to access their API token in the Salsify platform. We are actively investigating this issue. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. resolved Jun 29, 2026, 07:00 PM UTC

    We have confirmed access to the API tokens via SSO login is functioning as expected, and this incident is now 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 →

Major June 24, 2026 Shopify GraphQL publishes failing 4h 46m Syndication

Started Jun 24, 2026, 11:47 AM UTC· resolved Jun 24, 2026, 04:33 PM UTC

  1. investigating Jun 24, 2026, 11:47 AM UTC

    We are currently seeing all publishes for the Shopify GraphQL direct connection failing. This began on 6/24/26 at 11h15 UTC. Shopify is currently reporting issues in their systems which is causing the publishes to fail: https://www.shopifystatus.com/ We will continue to monitor Shopify's status to identify when the issue is resolved. Please reach out to Customer Support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. monitoring Jun 24, 2026, 12:37 PM UTC

    We are seeing Shopify publications go through successfully. The Shopify status page appears to have resolved the previous issues as well. If any previous publishes for Shopify failed, please republish to confirm. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. resolved Jun 24, 2026, 04:33 PM UTC

    We are seeing Shopify publications go through successfully. The Shopify status page appears to have resolved the previous issues as well. If any previous publishes for Shopify failed, please republish to confirm. 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 →

Minor June 19, 2026 Asset downloads populating with shareable URLs instead of asset names 1h 6m Salsify Application

Started Jun 19, 2026, 01:53 PM UTC· resolved Jun 19, 2026, 03:00 PM UTC

  1. investigating Jun 19, 2026, 01:53 PM UTC

    We are currently investigating an issue where downloading an asset from the asset detail page causes the file to save with its shareable URL populated as the filename instead of the actual asset name. Our engineering team is actively working to identify the root cause of this behavior. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. resolved Jun 19, 2026, 03:00 PM UTC

    The issue causing downloaded assets from the asset detail page to save with their shareable URL as the filename has been resolved. File downloads will now correctly populate with the designated asset name as expected. We appreciate your patience while our team worked to address this behavior. 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 →

Major June 10, 2026 Wayfair Item Setup - 'The system ran into an issue while checking your data' 1d 2h Syndication

Started Jun 10, 2026, 11:12 AM UTC· resolved Jun 11, 2026, 02:05 PM UTC

  1. investigating Jun 10, 2026, 11:12 AM UTC

    The following feedback is being returned in the Wayfair new item setup channels: '[Error] The system ran into an issue while checking your data. Please finish any other edits to this file, then upload it in Partner Home before downloading a new review file.' We have escalated this issue to Wayfair and they are currently working to determine the root cause along with resolving the issue. We will update as soon as we receive additional information. 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.

  2. resolved Jun 11, 2026, 02:05 PM UTC

    Wayfair has deployed a fix to resolve the error. We are seeing publishes complete successfully. Please try republishing any affected products and confirm. If you have any questions or if issue persists, 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.

Read the full incident report →

Major June 3, 2026 Shopify GQL Integration 1h 17m Syndication

Started Jun 03, 2026, 02:42 PM UTC· resolved Jun 03, 2026, 04:00 PM UTC

  1. 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.

  2. 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.

  3. 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 →

Major June 2, 2026 Amazon Publications Returning Submission Errors for the 'Is Refurbished' attribute 2d 2h Amazon

Started Jun 02, 2026, 07:58 AM UTC· resolved Jun 04, 2026, 10:46 AM UTC

  1. 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.

  2. 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.

  3. 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 →

Minor June 1, 2026 HEB Direct Connection Image Asset Errors 7d 22h Syndication

Started Jun 01, 2026, 07:02 PM UTC· resolved Jun 09, 2026, 05:57 PM UTC

  1. 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.

  2. 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.

  3. 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.

  4. 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 →

Major May 22, 2026 Walmart - It looks like there was a glitch feedback 17d 2h Walmart

Started May 22, 2026, 12:38 PM UTC· resolved Jun 08, 2026, 03:02 PM UTC

  1. identified May 22, 2026, 12:38 PM UTC

    The following feedback is being returned in the Walmart Omnispec channels: 'Product Submission Failed. FGW: It looks like there was a glitch. Please try again. If the problem persists, contact Walmart Partner Support. (ERR_INT_SYS_01010010)' We have escalated this issue to Walmart. Walmart has reviewed this issue and has let us know that the root cause of this feedback is due to products that are falling under review and being republished again before the products move out of the review state. Walmart is currently facing a delay reviewing any products that fall under this state and are working on the backlog so the recommendation in this case would be the following: 1. if you are receiving this feedback, please wait a couple of additional days outside of the recommended 48-72 hours before republishing to confirm if the product has moved out of the manual review state 2. using the activity ID provided in the feedback, you can search within your Supplier One portal to see if any additional feedback has been returned for products under review 3. if the products continue to receive this feedback, please open up a Walmart Support case to report this issue and escalate the Walmart Support case to your Walmart Merchant Please note that this issue may NOT occur to all products - only products stuck under review. We will provide additional updates about the reviews delay once we receive them. 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.

  2. resolved Jun 08, 2026, 03:02 PM UTC

    The following feedback is being returned in the Walmart Omnispec channels: 'Product Submission Failed. FGW: It looks like there was a glitch. Please try again. If the problem persists, contact Walmart Partner Support. (ERR_INT_SYS_01010010)' We have escalated this issue to Walmart. Walmart has reviewed this issue and has let us know that the root cause of this feedback is due to products that are falling under review and being republished again before the products move out of the review state. Please refer to the below steps if you are receiving this feedback: 1. if you are receiving this feedback, please wait the recommended 48-72 hours - it is recommended to stop republishing the products that are receiving this feedback immediately in the Walmart Omnispec channels 2. using the activity ID provided in the feedback, you can search within your Supplier One portal to see if any additional feedback has been returned for products under review 3. if there is no updates for the affected products within the recommended timeframe, please open up a Walmart Support case to report this issue with the relevant Activity ID, Supplier ID, and item details and escalate the Walmart Support case to your Walmart Merchant Please note that this issue may NOT occur to all products - only products stuck under review. We will provide additional updates about the reviews delay once we receive them. Walmart is currently working to improve the glitch feedback for clarity. 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.

Read the full incident report →

Notice April 29, 2026 Facebook Catalog Direct & Instagram Connection failing to syndicate 11h 59m Syndication

Started Apr 29, 2026, 02:23 AM UTC· resolved Apr 29, 2026, 02:23 PM UTC

  1. 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 →

Major April 21, 2026 Home Depot - Customers receiving 403 error response after channel publish 20h 37m The Home Depot

Started Apr 21, 2026, 05:55 PM UTC· resolved Apr 22, 2026, 02:33 PM UTC

  1. 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.

  2. 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.

  3. 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 →

Minor April 16, 2026 Renaming Smart Lists causing filter removal 17h 19m Salsify Application

Started Apr 16, 2026, 10:34 PM UTC· resolved Apr 17, 2026, 03:53 PM UTC

  1. 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.

  2. 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.

  3. 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 →

Major April 16, 2026 Digital Asset Feed generating blank export 1h 43m Salsify Application, Catalog Sites

Started Apr 16, 2026, 06:06 PM UTC· resolved Apr 16, 2026, 07:50 PM UTC

  1. 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.

  2. 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.

  3. 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 →

Major April 16, 2026 Walmart 1P Connector Publication Failures 1d Enhanced Content, Walmart

Started Apr 16, 2026, 09:22 AM UTC· resolved Apr 17, 2026, 09:22 AM UTC

  1. 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.

  2. 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.

  3. 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.

  4. resolved Apr 17, 2026, 09:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2026 Delayed Kroger Publications + Increase in Failed Intelligence Suite Workflow Tasks 1h 8m Salsify Application

Started Apr 14, 2026, 08:27 PM UTC· resolved Apr 14, 2026, 09:35 PM UTC

  1. 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.

  2. 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.

  3. 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 →

Critical March 17, 2026 Product Detail Pages failing to load 1h Salsify Application

Started Mar 17, 2026, 02:59 PM UTC· resolved Mar 17, 2026, 04:00 PM UTC

  1. 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.

  2. 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.

  3. 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 →