We continue to prepare for the daily deployment. We will provide a new update once we have visibility of whether the fix has been deployed and validated, or sooner if new information becomes available

Update timeline

1. identified Jun 10, 2026, 07:14 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Jun 10, 2026, 08:35 AM UTC

   We're currently investigating an issue impacting the Shopper Agent feature, which allows users to interact with a chat-based assistant to search for and discover products on their Storefront, is currently not responding. Customers may be unable to receive responses from the Shopper Agent Guided Chat experience, impacting AI-powered shopping assistance, product recommendations, and related conversational commerce workflows. This is a feature that commerce customers deploy to their storefronts. We have identified a change introduced as part of a recent release as the cause of the issue and are actively working on a fix to restore normal functionality.

3. monitoring Jun 10, 2026, 09:17 AM UTC

   We’ve confirmed the issue is across multiple instances including production and linked to a permission configuration change introduced as part of a recent release. Due to related database considerations, a rollback is not a viable option. We’re currently working on an emergency release to restore the permission configuration, which is estimated to take several hours to build, validate, and deploy. We will provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jun 10, 2026, 10:29 AM UTC

   We continue our efforts to prepare the fix and deploy it via an Emergency Release. Testing and approval activities are in progress. Following that, the plan is to deploy the ERR to all the impacted instances where this release was deployed, which is expected to take several hours. We’ll provide an update as soon as significant new information becomes available.

5. monitoring Jun 10, 2026, 12:13 PM UTC

   The fix has been successfully validated in a test environment. We're working to secure the necessary approvals to include this fix in the next scheduled deployment at 15:00 UTC. We'll provide an update following the deployment of the fix to the impacted instances.

6. monitoring Jun 10, 2026, 03:48 PM UTC

   The fix will be implemented with the next daily deployment, which is scheduled to begin at 00:30 UTC on June 11, 2026. We'll provide an update following the deployment of the fix, or sooner if additional information becomes available.

7. monitoring Jun 11, 2026, 01:56 AM UTC

   We continue to prepare for the daily deployment. We will provide a new update once we have visibility of whether the fix has been deployed and validated, or sooner if new information becomes available. We apologize for any inconvenience this issue is causing to customers.