Multiple Regions - Agents - Web Summary Tool Outage

Update timeline

1. investigating Mar 09, 2026, 04:41 PM UTC

   We are investigating reports of an outage impacting the Web Summary tool for Agents in Multiple Regions. Impact: Users may be unable to run deployed or debug Agents that rely on the Web Summary tool, causing those workflows to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

2. investigating Mar 09, 2026, 05:12 PM UTC

   We are investigating reports of an outage impacting the Web Summary tool used in RPA workflows and Agents in Multiple Regions. Impact: Users may be unable to run RPA workflows or deployed/debug Agents that rely on the Web Summary tool, which may cause those automations to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

3. identified Mar 09, 2026, 05:46 PM UTC

   We have identified the cause of the outage impacting the Web Summary tool for RPA workflows and Agents in Multiple Regions and are working on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Summary tool, which may cause those automations to fail. Next update: Our focus is on restoring service as quickly as possible.

4. identified Mar 09, 2026, 06:46 PM UTC

   We have identified the cause of the outage impacting the Web Summary tool for RPA workflows and Agents in Multiple Regions and are continuing to work on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Summary tool, which may cause those automations to fail. Next update: Our teams are actively working to restore service and will share updates as progress is made.

5. identified Mar 09, 2026, 07:36 PM UTC

   We have identified the cause of the outage impacting the Web Summary tool for RPA workflows and Agents in Multiple Regions and are continuing to work on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Summary tool, which may cause those automations to fail. Next update: Our teams are actively working to restore service and will share updates as progress is made.

6. monitoring Mar 09, 2026, 08:37 PM UTC

   We have identified the cause of the outage impacting the Web Summary tool for RPA workflows and Agents across multiple regions and have implemented a fix. Our teams are currently monitoring the environment to ensure the fix is stable and that services continue to operate normally. Next update: We will continue monitoring and provide further updates as we confirm sustained service stability.

7. resolved Mar 09, 2026, 08:41 PM UTC

   The issue impacting the Web Summary tool for RPA workflows and Agents across multiple regions has been resolved. Root cause was identified and a fix has been successfully implemented. Services have been restored and users should now be able to run RPA workflows and deployed or debug Agents that rely on the Web Summary tool without failure. Thank you for your patience while our teams worked to resolve the issue.

8. postmortem Mar 18, 2026, 11:54 PM UTC

   **Customer Impact** Between 16:28 UTC and 18:12 UTC \(about 1 hour 44 minutes\), the web summary tool experienced a service disruption. During this window, users were unable to execute summary-dependent tasks within Agents and RPA workflows, resulting in failed process executions. **Root Cause** The incident was triggered by an upstream API authentication failure. Specifically, the integration credentials for the third-party summary provider became invalidated due to an unexpected account configuration change on the provider's side. This led to the rejection of all outbound requests from our service. **Detection** The issue was first reported by a customer. ‌ **Resolution** To restore service, our engineering team provisioned a new API endpoint configuration and refreshed the associated security credentials. This successfully re-established the handshake with the provider, and restored full functionality. **Timeline** * **16:28 UTC:** Issue identified and investigation started. * **16:56 UTC:** Incident officially declared. * **17:00 UTC:** Root cause identified as an upstream credential failure. * **17:30 UTC:** Deployment of new API configuration started. * **17:53 UTC:** Deployment completed. Validation successful across production regions. * **18:12 UTC:** Incident resolved. Monitoring confirmed stability. **Follow-Up Actions** * Use detailed error-rate alerting to spot 4xx/5xx responses from upstream providers right away. This will reduce the reliance on customer reports. * Conduct a post-mortem with the service provider to ensure account configuration stability and prevent future credential invalidation.